Borrowing it
Nothing to install: this file belongs to rudraptpsingh/axon. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rudraptpsingh/axon/master/.claude/commands/mcp-test.mdgit clone --depth 1 https://github.com/rudraptpsingh/axonWrote 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/rudraptpsingh/axon/mcp-test)<a href="https://agentmods.dev/commands/rudraptpsingh/axon/mcp-test"><img src="https://agentmods.dev/badge/commands/rudraptpsingh/axon/mcp-test/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/rudraptpsingh/axon/mcp-test"><img src="https://agentmods.dev/badge/commands/rudraptpsingh/axon/mcp-test.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.00099 |
| Opus 5 | $0.00000 | $0.00049 |
| Sonnet 5 | $0.00000 | $0.00020 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
mcp-test 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 9d 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
Exercise all 7 MCP tools via the protocol.
Run: python3 scripts/mcp_exercise_all_tools.py ./target/release/axon
Report:
- Were all 7 tools found in tools/list? (hw_snapshot, process_blame, battery_status, system_profile, hardware_trend, session_health, gpu_snapshot)
- Did each tool return valid JSON with ok=true?
- Any errors, crashes, or unexpected responses?
- Did the axon serve process stay alive throughout?
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.
- 9d ago First seen · 10 lines · 0 tokens per session scan A 6ee679fc60c1
mcp-test is a command published in the GitHub repository rudraptpsingh/axon (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 99 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-31.
Other commands, from other repositories
init
Create or update the AgentBridge project config files in the current workspace.
ng-context-pack
Portable command prompt generated from skills/briefing-an-agent/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
ng-red-team
Portable command prompt generated from skills/stress-testing-agent-changes/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
verification-repair
PitWay: Bounded, approve-before-edit correction after every task is done.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.