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/markmhendrickson/neotoma/foundation_manage_error_debugginggit clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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/markmhendrickson/neotoma/foundation_manage_error_debugging)<a href="https://agentmods.dev/commands/markmhendrickson/neotoma/foundation_manage_error_debugging"><img src="https://agentmods.dev/badge/commands/markmhendrickson/neotoma/foundation_manage_error_debugging.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.00014 |
| Opus 5 | $0.00000 | $0.00007 |
| Sonnet 5 | $0.00000 | $0.00003 |
| Haiku 4.5 | $0.00000 | $0.00001 |
Grade A, and why
foundation_manage_error_debugging 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- manage_error_debugging — 100% identical, 0 lines differ
What it actually says
../../foundation/agent_instructions/cursor_commands/manage_error_debugging.md
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.
- 2d ago First seen · 1 lines · 0 tokens per session scan A 50c270f1e430
foundation_manage_error_debugging is a command published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 14 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-09-03.
Other commands, from other repositories
implement-fix
Implement fix from RCA document for GitHub issue.
analyze
Analyze the Kernel project architecture and provide insights.
cb-doctor
코드브레인 doctor — 실패한 체크만 한 줄씩.
cleaning
Диагностика и безопасная уборка проекта (или всего VPS) — инвентаризация следа, мёртвый код, дубли, конфликты, мусор. Тривиальные фиксы применяются сразу; рисковое — только по подтверждению.
diagnose
Trace a failed or stalled pipeline run — identify which FORGE annotation is missing or malformed, diagnose the failure point, and suggest specific remediation steps.
incident-response
Coordinate P0 incident response — hotfix validation, timeline reconstruction, and post-incident analysis.