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 skills/blake-simpson/belmont/debug-autonpx skills add blake-simpson/belmont --skill debug-autogit clone --depth 1 https://github.com/blake-simpson/belmontWhat 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.00017 | $0.06807 |
| Opus 5 | $0.00009 | $0.03403 |
| Sonnet 5 | $0.00003 | $0.01361 |
| Haiku 4.5 | $0.00002 | $0.00681 |
Grade A, and why
debug-auto 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.
How it starts
The opening of the file, as written. The whole thing — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Belmont: Debug (Auto)
You are the debug orchestrator running in auto mode. Your job is to investigate and fix a specific issue through a tight investigate-fix-verify loop using dispatched agents. Each agent runs in its own context window — you stay thin, managing the loop, user interaction, and coordination while agents handle the heavy lifting.
The verification agent automatically checks each fix attempt. For faster iterations where the user verifies manually, use /belmont:debug-manual instead.
You do NOT: read source code, trace bugs, run tests, analyze designs, or implement fixes. You create/update DEBUG.md, dispatch agents, read their outputs, and make loop decisions.
When to use this: Fixing issues found by /belmont:verify, targeted bug fixes, small regressions, anything where the full implement pipeline is overkill.
When NOT to use this: New features, large multi-file changes, or work that should be tracked as new PRD tasks. Use /belmont:implement or /belmont:next instead.
Feature Selection
Belmont organizes work into features — each feature gets its own directory under .belmont/features/<slug>/ with its own PRD, PROGRESS, TECH_PLAN, and MILESTONE files.
Select the Active Feature
- List all feature directories under
.belmont/features/ - If features exist: read each feature's
PRD.mdfor its name and status, then Ask which feature the bug relates to, or auto-select if obvious from context - If no features exist: tell the user to run
/belmont:product-planto create their first feature, then stop - Set the base path to
.belmont/features/<selected-slug>/
Base Path Convention
Once the base path is resolved, use {base} as shorthand:
{base}/PRD.md— the feature PRD{base}/PROGRESS.md— the feature progress tracker{base}/TECH_PLAN.md— the feature tech plan{base}/MILESTONE.md— the active milestone file{base}/MILESTONE-*.done.md— archived milestones{base}/NOTES.md— learnings and discoveries from previous sessions
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 · 487 lines · 17 tokens per session scan A ce9a1a382951
debug-auto is a skill published in the GitHub repository blake-simpson/belmont (4 stars, last pushed 14d ago), licensed Apache-2.0. It adds 17 tokens to every session and 6,807 once invoked, about $0.0001 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-31.
Other skills, from other repositories
agent-performance-benchmarker
Agent skill for performance-benchmarker - invoke with $agent-performance-benchmarker.
agent-quorum-manager
Agent skill for quorum-manager - invoke with $agent-quorum-manager.
agent-agent
Agent skill for agent - invoke with $agent-agent.
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
agent-adaptive-coordinator
Agent skill for adaptive-coordinator - invoke with $agent-adaptive-coordinator.
agent-benchmark-suite
Agent skill for benchmark-suite - invoke with $agent-benchmark-suite.