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/kmajerowicz/get-shit-right/debuggit clone --depth 1 https://github.com/kmajerowicz/get-shit-rightWhat 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.00011 | $0.00435 |
| Opus 5 | $0.00005 | $0.00217 |
| Sonnet 5 | $0.00002 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00044 |
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 3d 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
You are running the /gsr:debug command.
Working directory check: Before doing anything else, verify that pwd matches the user's project directory. If CLAUDE.md exists, check that the project name matches. If something looks wrong (you're in a different project's folder, or in a system directory), check .gsr-session.json in the current directory — it records the last known project directory. If it exists and points elsewhere, cd there. Otherwise, stop and ask the user to confirm the correct directory before proceeding.
Session manifest: After confirming the working directory, write .gsr-session.json in the project root:
{ "project_dir": "<absolute path>", "project_name": "<from CLAUDE.md or scope>", "last_command": "gsr:debug", "timestamp": "<ISO 8601>" }
Update this file (don't recreate) if it already exists — preserve project_dir and project_name, update last_command and timestamp.
Invocation variants:
/gsr:debug— no argument: scandocs/debug/for files withstatus: activein frontmatter. If any exist, present them conversationally: "Here are your active debug sessions: [slug — feature, last updated]. Pick one to resume, or tell me what's broken to start a new one." If none exist, prompt for a symptom and start a new session./gsr:debug resume <slug>— loaddocs/debug/<slug>.mddirectly, continue from Current Focus + Next Step.
Load and execute the debug skill: read ${CLAUDE_PLUGIN_ROOT}/skills/debug/SKILL.md in full, then follow its instructions exactly.
When a debug session is resolved, tell the user:
Session resolved and saved to
docs/debug/<slug>.md. Return to build with/gsr:build, or start another debug session with/gsr:debug.
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.
- 3d ago First seen · 25 lines · 11 tokens per session scan A 81a8aa077091
debug is a command published in the GitHub repository kmajerowicz/get-shit-right (5 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 435 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 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.