Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add codemie-ai/codemie-code/plugin install codemieWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/codemie-ai/codemie-code/codemie-subagents)<a href="https://agentmods.dev/commands/codemie-ai/codemie-code/codemie-subagents"><img src="https://agentmods.dev/badge/commands/codemie-ai/codemie-code/codemie-subagents/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/codemie-ai/codemie-code/codemie-subagents"><img src="https://agentmods.dev/badge/commands/codemie-ai/codemie-code/codemie-subagents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00026 | $0.02729 |
| Opus 5.5 | $0.00010 | $0.01092 |
| Sonnet 5.5 | $0.00005 | $0.00546 |
| Haiku 4.5 | $0.00003 | $0.00273 |
Grade A, and why
codemie-subagents scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codemie Subagents - Generate Project-Specific Subagent Files
Command Name: codemie-subagents
Description: Generate project-specific subagent files from templates by analyzing codebase and existing guides
Output: AI-optimized subagent definitions in .claude/agents/
Additional user's input
Additional context/input from user: $ARGUMENTS. Might be empty by default.
Purpose
Analyze project and generate tailored subagent files:
- Unit Tester Agent - Project's testing patterns and framework
- Solution Architect Agent - Project's architecture and conventions
- Code Review Agent - Project's code standards and linting rules
- Refactor Cleaner Agent - Project's cleanup tools and critical paths
Prerequisites
- Project is accessible
- Templates exist at
${CLAUDE_PLUGIN_ROOT}/claude-templates/templates/agents/ - (Optional) Backup existing
.claude/agents/if updating agents
Safety Note: If existing agents are found, original content will be preserved during updates. However, creating a backup before running this command is recommended for recovery purposes.
🚨 SIZE LIMITS
Each generated subagent: 150-300 lines maximum
| ✅ Do | ❌ Don't |
|---|---|
| Brief examples (10-15 lines) | Extensive code blocks |
| Tables for patterns | Long prose explanations |
| File:line references | Full code listings |
| One example per pattern | Multiple variations |
Execution
Phase 1: Discovery
Step 1.1: Find Templates
ls ${CLAUDE_PLUGIN_ROOT}/claude-templates/templates/agents/
Expected: code-review-agent-template.md, solution-architect-agent.md, unit-tester-agent.md, refactor-cleaner-agent.md
If no templates found → Report error and stop.
Step 1.1b: Check Existing Agents
ls .claude/agents/ 2>/dev/null
Purpose: Identify existing agents to update rather than recreate
Agent Name Variations to Match:
| Template | Possible Existing Names |
|---|---|
| unit-tester-agent.md | unit-tester.md, tester.md, unit-test-agent.md, test-agent.md |
| solution-architect-agent.md | solution-architect.md, architect.md, architecture-agent.md |
| code-review-agent.md | code-review.md, reviewer.md, review-agent.md, code-reviewer.md |
| refactor-cleaner-agent.md | refactor-cleaner.md, refactor.md, cleaner.md, cleanup-agent.md |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 350 lines · 26 tokens per session scan A 945b32a0ccb9
codemie-subagents is a command published in the GitHub repository codemie-ai/codemie-code (302 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 2,729 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.