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.
npx agentmods add commands/mock-server/mockserver-monorepo/agent-statusgit clone --depth 1 https://github.com/mock-server/mockserver-monorepoWrote 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/mock-server/mockserver-monorepo/agent-status)<a href="https://agentmods.dev/commands/mock-server/mockserver-monorepo/agent-status"><img src="https://agentmods.dev/badge/commands/mock-server/mockserver-monorepo/agent-status.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00262 |
| Opus 5 | $0.00018 | $0.00131 |
| Sonnet 5 | $0.00007 | $0.00052 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
agent-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 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.
What it actually says
Run .opencode/scripts/agent-status.sh and print its output verbatim. The script reads .worktrees/agent-* under the repo root and renders a table.
If the user is in a worktree themselves (i.e. git rev-parse --show-toplevel is inside .worktrees/), highlight which row corresponds to the current worktree in the response (the row whose ID matches the suffix of the current worktree dir name).
If no worktrees are active, the script will say so — just relay that message; don't suggest creating one unless the user asks.
Recommend the convention to record activity for the dashboard: when an agent is working in a worktree, write the current activity to .tmp/agent-activity in that worktree (one line, e.g. echo "Running mvn verify" > .tmp/agent-activity). The next /agent-status run will surface it. See .opencode/rules/worktree-workflow.md for the convention details.
If the user provided additional instructions: $ARGUMENTS
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 · 13 lines · 36 tokens per session scan A 213adda9511f
agent-status is a command published in the GitHub repository mock-server/mockserver-monorepo (4,964 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 262 once invoked, about $0.0002 per session on Opus 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
write-fixtures
../../skills/write-fixtures/SKILL.md.
bench
Refresh model grades (capability + price, from benchlm.ai and OpenRouter) or measure route latency through the proxy. Nothing runs automatically — this is the manual refresh.
models
List every model reachable through cc-proxy with the provider each routes to.
bmad-architecture
Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".
bmad-advanced-elicitation
Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.
bmad-agent-dev
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.