Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/vanzan01/claude-code-sub-agent-collectiveWrote 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/vanzan01/claude-code-sub-agent-collective/mock)<a href="https://agentmods.dev/commands/vanzan01/claude-code-sub-agent-collective/mock"><img src="https://agentmods.dev/badge/commands/vanzan01/claude-code-sub-agent-collective/mock/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/vanzan01/claude-code-sub-agent-collective/mock"><img src="https://agentmods.dev/badge/commands/vanzan01/claude-code-sub-agent-collective/mock.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.00000 | $0.00389 |
| Opus 5.5 | $0.00000 | $0.00156 |
| Sonnet 5.5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
mock 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 2mo 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.
What it actually says
/mock - Mock Agent Testing Command
allowed-tools: Task(*) description: 🧪 Test agent handoff coordination using ONLY mock agents - complete isolation from real agents
Purpose
Test complete agent handoff chains using ONLY mock agents. This command routes exclusively to mock agents to validate coordination patterns without touching any real implementation agents.
Mock Agent Routing
Mock Chain Flow
/mock → mock-prd-research-agent → mock-project-manager-agent → mock-implementation-agent → mock-testing-agent → mock-quality-gate-agent → mock-completion-agent
Available Mock Agents ONLY
mock-prd-research-agent- Mock PRD analysismock-project-manager-agent- Mock project coordinationmock-implementation-agent- Mock development simulationmock-testing-agent- Mock testing simulationmock-quality-gate-agent- Mock quality validationmock-completion-agent- Mock delivery simulation
Execution
For ANY mock testing request, route to mock-prd-research-agent:
Task(subagent_type="mock-prd-research-agent",
description="Mock chain testing",
prompt="Start complete mock agent handoff chain simulation using mock PRD at .taskmaster/docs/mock-prd.txt - test all handoff patterns through mock-project-manager-agent → mock-implementation-agent → mock-testing-agent → mock-quality-gate-agent → mock-completion-agent")
Usage Examples
/mock "test handoff chain"/mock "validate agent coordination"/mock "test complete workflow"
Critical Rules
- NEVER route to real agents (prd-research-agent, component-implementation-agent, etc.)
- ALWAYS start with mock-prd-research-agent
- ONLY test coordination patterns, no real implementation
- Use mock PRD at .taskmaster/docs/mock-prd.txt
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.
- 2mo ago First seen · 45 lines · 0 tokens per session scan A eb70337d3974
mock is a command published in the GitHub repository vanzan01/claude-code-sub-agent-collective (525 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 389 tokens. 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.
mock compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| mockvanzan01/claude-code-sub-agent-collective | Command | 525 | 6mo ago | MIT | A | 0 | Claude Code |
| review-pryonatangross/orchestkit | Command | 299 | yesterday | MIT | A | 40 | Claude Code, Cursor |
| fix-issueyonatangross/orchestkit | Command | 299 | yesterday | MIT | A | 45 | Claude Code, Cursor |
| implementyonatangross/orchestkit | Command | 299 | yesterday | MIT | A | 50 | Claude Code, Cursor |
| verifyyonatangross/orchestkit | Command | 299 | yesterday | MIT | A | 55 | Claude Code, Cursor |
| create-pryonatangross/orchestkit | Command | 299 | yesterday | MIT | A | 46 | Claude Code, Cursor |
| design-to-codeyonatangross/orchestkit | Command | 299 | yesterday | MIT | A | 54 | Claude Code, Cursor |