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/samibs/skillfoundry/debuggit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/debug)<a href="https://agentmods.dev/commands/samibs/skillfoundry/debug"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/debug.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 | $0.00000 | $0.00574 |
| Opus 5 | $0.00000 | $0.00287 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
debug 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 yesterday.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug — Interactive Debugger
Role: Launch and control an interactive debug session for a file, test, or running process.
Usage
/debug <file> Start debug session, paused at entry
/debug <file>:<line> Start session with breakpoint at line
/debug test <test-file> Debug a test file using its test runner
Examples
/debug src/auth/login.ts
/debug src/utils/parser.ts:42
/debug test src/auth/__tests__/login.test.ts
Behavior
When invoked, follow this sequence:
1. Start Session
- Parse the argument to extract file path and optional line number.
- If prefixed with
test, detect the test runner (jest, vitest, pytest, mocha) from project config. - Call
debug_startwith the resolved file, runtime, and test_command if applicable. - Confirm the session started and report the paused location.
2. Set Initial Breakpoint (if line specified)
- If the user provided
<file>:<line>, calldebug_breakpointwith actionsetat that line. - Then call
debug_stepwith actioncontinueto run to the breakpoint. - Report the paused location and surrounding code context.
3. Guide Inspection
- Once paused, call
debug_inspectwith targetscopeto show local variables. - Call
debug_inspectwith targetcallstackto show the call stack. - Present findings and ask the user what to investigate next.
4. Interactive Loop
Respond to user instructions by mapping them to debug tools:
| User says | Tool call |
|---|---|
| "step" / "next" | debug_step action=next |
| "step into" | debug_step action=into |
| "step out" | debug_step action=out |
| "continue" | debug_step action=continue |
| "inspect X" | debug_inspect target=X |
| "eval " | debug_evaluate expression=expr |
| "break :" | debug_breakpoint action=set |
| "breakpoints" | debug_breakpoint action=list |
| "stop" / "quit" | debug_stop |
5. Cleanup
- Always call
debug_stopwhen the user is done or the process exits. - Report any uncaught exceptions with full stack trace and variable context.
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.
- yesterday First seen · 76 lines · 0 tokens per session scan A a6cd80856467
debug is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 574 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.