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/rudraptpsingh/axon/fix-buggit 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/fix-bug)<a href="https://agentmods.dev/commands/rudraptpsingh/axon/fix-bug"><img src="https://agentmods.dev/badge/commands/rudraptpsingh/axon/fix-bug.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.1 | $0.00000 | $0.00235 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
fix-bug 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 5d 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
Investigate and fix a bug in axon's signal quality.
Follow this protocol:
- Identify which signal is wrong (from the last /eval, /diagnose, or /stress-test output the user provides)
- Read the relevant source files:
- Types and data models: crates/axon-core/src/types.rs
- Impact scoring: crates/axon-core/src/impact.rs
- Collector loop: crates/axon-core/src/collector.rs
- Alerts: crates/axon-core/src/alerts.rs
- Thresholds: crates/axon-core/src/thresholds.rs
- MCP server tools: crates/axon-server/src/lib.rs
- CLI entry: crates/axon-cli/src/main.rs
- Make the minimal fix — change the least code necessary
- Add a unit test if the fix changes thresholds or scoring logic
- Run
cargo test --workspace— all must pass - Rebuild:
cargo build --release - Re-run the scenario that exposed the bug and verify the fix
- Report: what was wrong, root cause, what changed, before vs after
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.
- 5d ago First seen · 19 lines · 0 tokens per session scan A 49422136e271
fix-bug 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 235 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
od-contribute
Open a first-contribution PR (or bug issue) on nexu-io/open-design — works for non-coders too.
mt-impact
Shortcut to the canonical Memtrace impact analysis skill.
mt-onboard
Shortcut to the canonical Memtrace codebase exploration skill.
mt-preflight
Shortcut to the canonical Memtrace preflight skill.
mt-recall
Shortcut to the canonical Memtrace decision-memory skill.
memory-check
Validate INTERNALRAG (index + validate + status + guard).