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/spencermarx/open-code-reviewWrote 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/spencermarx/open-code-review/status)<a href="https://agentmods.dev/commands/spencermarx/open-code-review/status"><img src="https://agentmods.dev/badge/commands/spencermarx/open-code-review/status/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/spencermarx/open-code-review/status"><img src="https://agentmods.dev/badge/commands/spencermarx/open-code-review/status.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.00331 |
| Opus 5.5 | $0.00000 | $0.00132 |
| Sonnet 5.5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
status 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.
This is a copy
100% identical to status — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Check Coordination Status
🎯 Key Principle
This tool coordinates Claude Code's actions. It does NOT write code or create content.
MCP Tool Usage in Claude Code
Tool: mcp__claude-flow__swarm_status
Parameters
{
"swarmId": "current"
}
Description
Monitor the effectiveness of current coordination patterns
Details
Shows:
- Active coordination topologies
- Current cognitive patterns in use
- Task breakdown and progress
- Resource utilization for coordination
- Overall system health
Example Usage
In Claude Code:
- Check swarm status: Use tool
mcp__claude-flow__swarm_status - Monitor in real-time: Use tool
mcp__claude-flow__swarm_monitorwith parameters{"interval": 1000} - Get agent metrics: Use tool
mcp__claude-flow__agent_metricswith parameters{"agentId": "agent-123"} - Health check: Use tool
mcp__claude-flow__health_checkwith parameters{"components": ["swarm", "memory", "neural"]}
Important Reminders
- ✅ This tool provides coordination and structure
- ✅ Claude Code performs all actual implementation
- ❌ The tool does NOT write code
- ❌ The tool does NOT access files directly
- ❌ The tool does NOT execute commands
See Also
- Main documentation: /CLAUDE.md
- Other commands in this category
- Workflow examples in /workflows/
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 · 47 lines · 0 tokens per session scan A eb0de483f7b5
status is a command published in the GitHub repository spencermarx/open-code-review (380 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 331 tokens. A static security scan graded it A with 0 findings. It is 100% identical to status, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
growth-email
Create transactional and marketing email templates.
guardrails
Show guardrails status, switch modes, set token cap, or view the audit log. Usage: /guardrails [status|log|strict|relaxed|audit|reset|policy|tokencap].
environment-switching-local-cloud-ssh
The environment selector at the bottom of Claude Code switches where work executes: local for fast interactive iteration, cloud (Anthropic servers) for routines that must run with your machine off, SSH for driving a remote box like a VPS.
complete
Signal that a skill's work is complete. Triggers downstream subscriptions with "when": "complete" timing. Automatically invoked — do not run manually.
legal-5step
Execute the BetterCallClaude 5-step Swiss legal framework: intake → research → strategy → adversarial → draft. A complete end-to-end pipeline for any Swiss legal matter, from document analysis through final legal output.