plugins/claude-cli/skills/claude-cli-agent/SKILL.md
Claude CLI sub-agent system for persona-based analysis. Use when piping large contexts to Anthropic models for security audits, architecture reviews, QA analysis, or any specialized analysis requiring a fresh model context.
npx skillsauth add richfrem/agent-plugins-skills claude-cli-agentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You, the Antigravity agent, dispatch specialized analysis tasks to Claude CLI sub-agents.
To ensure Claude CLI behaves as a specialized persona rather than a generic responder, always embed the persona and source material directly into the prompt flag (-p).
claude --model haiku-4.5 -p "$(cat agents/persona.md)
---SOURCE CODE---
$(cat target.py)
---INSTRUCTION---
Perform a full code review. Use severity levels: 🔴 CRITICAL, 🟡 MODERATE, 🟢 MINOR.
You are operating as an isolated sub-agent.
Do NOT use tools. Do NOT access filesystem." > review.md
run_agent.py (Cross-Platform)For reusable sub-agent execution, use the provided Python orchestrator which handles temp file assembly and prompt concatenation reliably across Windows, macOS, and Linux.
# Location: plugins/claude-cli/scripts/run_agent.py
python ./scripts/run_agent.py <PERSONA_FILE> <INPUT_FILE> <OUTPUT_FILE> "<INSTRUCTION>"
python ./scripts/run_agent.py agents/security-auditor.md target.py security.md \
"Find vulnerabilities. Use severity levels: 🔴 CRITICAL, 🟡 MODERATE, 🟢 MINOR."
agents/)These personas are mirrored from the Gemini and Copilot plugins to ensure consistent "Agentic" analysis across the ecosystem.
| Persona | Use For |
|:---|:---|
| security-auditor.md | Red team, vulnerability scanning, threat modeling |
| refactor-expert.md | Optimizing code for readability, performance, and DRY |
| architect-review.md | Assessing system design, modularity, and complexity |
For rapid, cost-effective analytical sub-agent tasks, always specify --model haiku-4.5. It provides the best latency for "Inner Loop" code reviews.
If your prompt starts with YAML frontmatter (e.g., ---), some shell parsers might misinterpret the flag. Always prepend a newline to the prompt string when passing it to -p. (Note: The run_agent.py script handles this automatically).
Always add these instructions to your dispatch prompt to prevent the sub-agent from attempting to use external tools:
"You are operating as an isolated sub-agent. Do NOT use tools. Do NOT access filesystem. Only use the provided input."
python ./scripts/run_agent.py agents/refactor-expert.md target.py output.md "Refactor this code."
tools
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>
data-ai
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>
testing
Audit Vector DB coverage -- compares the live filesystem manifest against the ChromaDB index to identify coverage gaps.
development
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.