richfrem/create-sub-agent
plugins/agent-scaffolders/skills/create-sub-agent/SKILL.md
Design and scaffold a Claude Code sub-agent
$ 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: May 18, 2026, 5:18 AM126.2s87 files scanned
SKILL.md
- name:
- create-sub-agent
- plugin:
- agent-scaffolders
- description:
- Design and scaffold a Claude Code sub-agent
- 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/vector-db-ingest
tools
VerifiedTrustedCommunity
Ingests repository files into the ChromaDB vector store. Builds or updates the vector index from a manifest or directory scan using ingest.py. Use when new files need to be indexed or the vector store is out of date. <example> user: "Index these new plugin files into the vector database" assistant: "I'll use vector-db-ingest to add them to the vector store." </example> <example> user: "The vector store is missing recent files -- update it" assistant: "I'll use vector-db-ingest to re-index the changes." </example>
3SKILL.mdUpdated Jun 2, 2026
richfrem/vector-db-cleanup
data-ai
VerifiedTrustedCommunity
Removes stale and orphaned chunks from the ChromaDB vector store for files that have been deleted or renamed. Use after files are removed or moved to keep the vector index in sync with the filesystem. <example> user: "Clean up the vector store after I deleted some files" assistant: "I'll use vector-db-cleanup to remove orphaned chunks." </example> <example> user: "The vector database has chunks for files that no longer exist" assistant: "I'll run vector-db-cleanup to prune them." </example>
3SKILL.mdUpdated Jun 2, 2026
richfrem/vector-db-audit
testing
VerifiedTrustedCommunity
Audit Vector DB coverage -- compares the live filesystem manifest against the ChromaDB index to identify coverage gaps.
3SKILL.mdUpdated Jun 2, 2026
richfrem/rlm-search
development
VerifiedTrustedCommunity
3-Phase Knowledge Search strategy for the RLM Factory ecosystem. Auto-invoked when tasks involve finding code, documentation, or architecture context in the repository. Enforces the optimal search order: RLM Summary Scan (O(1)) -> Vector DB Semantic Search -> Grep/Exact Match. Never skip phases.
3SKILL.mdUpdated Jun 2, 2026