A command for testing whether a chain of software agents hands work to one another correctly. It uses simulated agents, so the test does not run real implementation work.

It is for simulating a complete workflow from requirements research through project management, implementation, testing, quality checks, and completion.

It provides an isolated way to check routing and coordination without changing the actual project or involving real development agents.

mock — Command for coding agents by vanzan01: A command for testing whether a chain of software…

Install

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.

agentmods

npx agentmods add commands/vanzan01/claude-code-sub-agent-collective/mock

Clone the repo

git clone --depth 1 https://github.com/vanzan01/claude-code-sub-agent-collective

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/vanzan01/claude-code-sub-agent-collective/mock.svg)](https://agentmods.dev/commands/vanzan01/claude-code-sub-agent-collective/mock)

Your own site

<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="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 389 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.00389
Opus 5	$0.00000	$0.00195
Sonnet 5	$0.00000	$0.00078
Haiku 4.5	$0.00000	$0.00039

Measured 4d ago against content hash eb70337d3974, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 4d 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.

templates/commands/mock.md · 45 lines

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 analysis
mock-project-manager-agent - Mock project coordination
mock-implementation-agent - Mock development simulation
mock-testing-agent - Mock testing simulation
mock-quality-gate-agent - Mock quality validation
mock-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

Changes

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.

4d ago First seen · 45 lines · 0 tokens per session scan A eb70337d3974

Subscribe to this mod's changes

mock is a command published in the GitHub repository vanzan01/claude-code-sub-agent-collective (521 stars, last pushed 4mo 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.

Building agents Testing agents ai-development claude claude-code taskmaster yolo

assess

Assesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use…

yonatangross/orchestkit · 72 tokens

brainstorm

Design exploration using parallel agents through a 7-phase process: topic analysis, memory context, divergent ideation (10+ ideas), feasibility filtering, evaluation with devil's advocate scoring (0-10 across 7 dimensions), synthesis of top approaches, and trade-off comparison. Supports open exploration, constrained…

yonatangross/orchestkit · 87 tokens

fix-issue

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…

yonatangross/orchestkit · 82 tokens

implement

Full-power feature implementation using parallel subagents for backend, frontend, testing, and security, with worktree isolation and quality verification in one workflow. Chains with /ork:cover for tests and /ork:verify for validation. Use when asked to build, add, create, scaffold, or set up a new feature, endpoint…

yonatangross/orchestkit · 91 tokens

review-pr

PR review using parallel specialized agents for code quality, security, testing, architecture, and performance analysis. Synthesizes findings into a review report with conventional comments (praise/issue/suggestion/nitpick) and approve or request-changes verdict. Use when reviewing pull requests, conducting security…

yonatangross/orchestkit · 69 tokens

verify

Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…

yonatangross/orchestkit · 92 tokens