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/xsovad06/sova/debuggit clone --depth 1 https://github.com/xsovad06/sovaWhat 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.00019 | $0.00521 |
| Opus 5 | $0.00010 | $0.00260 |
| Sonnet 5 | $0.00004 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
debug scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Try to reproduce the issue (via test, curl, or browser) How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging
Debug an issue in the project.
Problem description: $ARGUMENTS
Workflow
1. Reproduce
- Understand the problem from the description
- Check application logs for errors
- Try to reproduce the issue (via test, curl, or browser)
- If the issue is unclear, ask the user for more details
2. Locate
- Identify the relevant code path (URL -> view/controller -> service -> model)
- Read the relevant source files to understand the flow
- Check recent changes with
git log --oneline -10andgit diff-- was something recently changed? - Search for related error messages in the codebase
3. Diagnose
- Trace the execution flow from entry point to the error
- Identify the root cause -- not just the symptom
- Check common issues:
- Missing migrations or schema changes
- Import errors / circular imports
- Configuration mismatches between environments
- Authentication/permission issues
- Database constraint violations
- Race conditions or state management bugs
4. Fix
- Apply the minimal fix that addresses the root cause
- Do not introduce workarounds -- fix the actual problem
- If the fix touches multiple files, explain the connection
- Scout rule: while in each file, fix any pre-existing issues you notice (lint warnings, dead imports, obvious bugs adjacent to your fix). Keep scout fixes small and low-risk.
5. Verify
- Write a test that reproduces the original issue (should fail before fix, pass after)
- Run the project's test suite (see CLAUDE.md for commands)
- Check that no regressions were introduced
- Verify application logs are clean
6. Prevent
- If this bug class could recur, suggest a test that would catch it
- If it was caused by a missing convention, suggest updating AGENTS.md or project guidelines
Cross-References
- Need to run tests? Run
/testto iterate on failures - Want a review of the fix? Run
/reviewbefore pushing
Rules
- NEVER use emojis in any output
- Focus on root cause, not symptoms
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 · 69 lines · 19 tokens per session scan A 81b35a811a19
debug is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 521 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
create-command
Create a new obsidian-second-brain command via interview - zero markdown editing required.
obsidian-architect
Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions. Re-run to refresh without clobbering your edits.
obsidian-visualize
Generate a visual canvas map of your vault - see the shape of your second brain and how knowledge connects.
obsidian-export
Export a clean structured snapshot of the vault that any agent or tool can consume - flat JSON, markdown index, or an OKF (Open Knowledge Format) bundle.
obsidian-retrieval-eval
Measure how well vault search finds the right note for a natural-language question - recall@k and MRR, with the concrete failures.
obsidian-reindex
Refresh the vault's semantic search index and report coverage before and after.