richfrem/create-sub-agent
plugins/agent-scaffolders/skills/create-sub-agent/SKILL.md
Scaffolds a new autonomous sub-agent with its own prompt, system instructions, and tool permissions. NOT for stateless procedural skills (use `create-skill`) and NOT for creating GitHub Actions workflows (use `create-agentic-workflow`).
$ install --global
skillsauthnpx skillsauth add richfrem/agent-plugins-skills create-sub-agentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 13, 2026, 6:06 AM202.2s87 files scanned
SKILL.md
- name:
- create-sub-agent
- plugin:
- agent-scaffolders
- description:
- >
- argument-hint:
- [agent-name or use-case description]
- allowed-tools:
- Bash, Read, Write
Follow the create-sub-agent skill workflow to design and generate a Claude Code agent file.
Inputs
$ARGUMENTS— optional agent name or brief use-case description passed as initial context to the design interview. Omit to start with open discovery.
Steps
- If
$ARGUMENTSis provided, use it as the starting context for agent name / purpose - Follow the create-sub-agent phased workflow: extract core intent via design interview
(purpose, input/output contract, escalation posture, tools, permissions.deny, model,
maxTokens, color, lifecycle hooks, placement), present design summary, confirm,
then generate the agent
.mdfile - Validate the generated agent with
validate_agent.py - Publication Check: Ask if the agent should be visible to GitHub Copilot or Claude Code for this repository. If yes, materialize it into
.github/agents/or.claude/agents/and ensure the path is tracked in.gitignore. - Report the created agent path, triggering conditions, and next steps
Output
Agent .md file with complete YAML frontmatter (name, description with <example> blocks,
model, maxTokens, color, permissions.allowedTools, permissions.deny) and a second-person
system prompt targeting 500-3,000 characters.
Placement Rules
Plugin agents: flat .md file — plugins/<plugin-name>/agents/<agent-name>.md
- No subdirectory. Skills use
skills/<name>/SKILL.mdsubdirectory format, but agents do NOT. - Confirmed against Anthropic official plugins (
feature-dev,code-simplifier,hookify).
Local/project agents: .claude/agents/<agent-name>.md (also flat, no subdirectory).
Discovery & Publication
To make an agent visible to GitHub Copilot or Claude Code for this repository, follow the Discovery-First Publication pattern:
- Materialize the agent into
.github/agents/(Copilot) or.claude/agents/(Claude). - Ensure
.gitignoreallows the specific agent file or subdirectory. - Commit the materialized file to the repository.
See Agent Discovery and Publication Pattern for details.
Edge Cases
- If
$ARGUMENTSis empty: conduct the full Phase 1 design interview — do not pre-fill - If an agent with that name already exists: confirm before overwriting
- If requirements suggest multiple responsibilities: propose splitting into specialized agents
- If high-risk operations are required: configure escalation posture and add Stop hook
Related Skills
richfrem/issue-worktree-agent
testing
VerifiedTrustedCommunity
Skill for creating and managing isolated git worktrees (`.worktrees/issue-NNN`) for issue execution branches. USE ONLY when setting up or cleaning up isolated git worktrees for specific issue execution. DO NOT USE for managing local task files (use `task-agent`) or escalating tasks to issues (use `github-issue-backlog-agent`).
4SKILL.mdUpdated Jul 29, 2026
richfrem/issue-pr-lifecycle-agent
data-ai
VerifiedTrustedCommunity
Skill for orchestrating the end-to-end GitHub issue lifecycle flow: Issue -> Worktree -> Implementation -> PR Creation -> Resolution Closure. USE ONLY when running or dry-running full lifecycle orchestration for resolving an issue with a PR. DO NOT USE for isolated worktree management only (use `issue-worktree-agent`) or logging issues (use `github-issue-agent`).
4SKILL.mdUpdated Jul 29, 2026
richfrem/github-issue-prioritizer
tools
VerifiedTrustedCommunity
Automatically ranks GitHub issues (P0-P3) based on friction tier, frequency, and blockages, synchronizing priority labels and GitHub Projects v2 custom fields.
4SKILL.mdUpdated Jul 29, 2026
richfrem/github-issue-backlog-agent
testing
VerifiedTrustedCommunity
Bridge skill for escalating ephemeral local task scratchpad items (`tasks/*.md`) into durable, taxonomy-validated, evidence-rich GitHub Issues. USE ONLY when promoting a single-session local task into durable repository backlog. DO NOT USE for managing local kanban boards (use `task-agent` instead) or directly querying/commenting on issues (use `github-issue-agent` instead).
4SKILL.mdUpdated Jul 29, 2026