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/bherbruck/mcp-debugger/stepgit clone --depth 1 https://github.com/bherbruck/mcp-debuggerWhat 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.00009 | $0.00261 |
| Opus 5 | $0.00005 | $0.00130 |
| Sonnet 5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
step 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.
What it actually says
Step Through Code
Stepping $ARGUMENTS.direction in the current debug session.
Step Directions
step in
Use step_in to:
- Enter the next function call
- Go into library code if needed
- Useful when you want to understand what a function does
step over
Use step_over to:
- Execute the current line completely
- Move to the next line without entering function calls
- Most common stepping action
step out
Use step_out to:
- Complete the current function
- Return to the caller
- Useful when you've seen enough of the current function
After Each Step
- Use
get_source_contextto show where we are now - Use
get_variablesto see current variable values - Highlight any changes from the previous state
- Explain what just happened
Continue Execution
If you want to run until the next breakpoint instead of stepping:
- Use
continueto resume normal execution - Use
pauseto interrupt running code
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 · 46 lines · 9 tokens per session scan A f3b05f8ed747
step is a command published in the GitHub repository bherbruck/mcp-debugger (2 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 261 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.