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/sijeeshmiziha/visionagent/debuggit clone --depth 1 https://github.com/sijeeshmiziha/visionagentWhat 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.00319 |
| Opus 5 | $0.00000 | $0.00160 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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 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
Debug Issue
Diagnose and fix a bug or failing test in VisionAgent.
Arguments
$ARGUMENTS (Describe the issue, error message, or paste the failing test output)
Debug Process
1. Reproduce
If given a test name or file:
npx vitest run tests/path/to/failing.test.ts
If given an example:
npm run example -- examples/<module>/<example>.ts
Capture the full error output.
2. Locate the Root Cause
- Read the stack trace carefully — identify the exact file and line
- Read that file and the files it calls
- Trace the data flow from input to the failure point
- Check TypeScript types (run
npm run typecheckto surface type errors)
3. Understand Before Fixing
- Read the failing test to understand what behavior it expects
- Read the implementation to understand what it currently does
- Identify the gap
4. Fix
- Make the minimal change that fixes the issue
- Do NOT refactor or clean up surrounding code unless it's causing the bug
- Do NOT add features while fixing bugs
5. Verify
npm test # All tests must pass
npm run typecheck # No type errors
npm run lint # No lint errors
6. Check for Regression
npm run ci
Report: root cause, the fix applied (file:line), and CI status.
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 · 62 lines · 0 tokens per session scan A 11e94c6a492e
debug is a command published in the GitHub repository sijeeshmiziha/visionagent (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 319 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
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
workflow-classify
Classify task size (S/M/L/XL) and recommend the appropriate workflow pipeline.
test-tools
Test MCP NixOS Tools (project).
firm
Convene your standing AI staff — memos on every beat, a board session without you, minutes with dissent preserved.
ship-a-feature
Workflow recipe — take a feature idea from fuzzy brief to launch plan by chaining 5 skills.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.