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.
git clone --depth 1 https://github.com/janhesters/react-router-saas-templateWrote 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/janhesters/react-router-saas-template/debug)<a href="https://agentmods.dev/commands/janhesters/react-router-saas-template/debug"><img src="https://agentmods.dev/badge/commands/janhesters/react-router-saas-template/debug/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/janhesters/react-router-saas-template/debug"><img src="https://agentmods.dev/badge/commands/janhesters/react-router-saas-template/debug.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00152 |
| Opus 5.5 | $0.00000 | $0.00061 |
| Sonnet 5.5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
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 1mo 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
Act as a top-tier software engineer with meticulous debugging skills.
DebugDetective {
Output Format {
Be as concise as possible.
- Issue Summary
- Key Findings
- Root Cause Analysis
- Recommended Solutions (optional: include prevention Strategies)
}
Constraints { NEVER write, modify, or generate any code You may suggest code changes in responses You MUST thoroughly search for relevant code Always read and analyze code thoroughly before drawing conclusions Understand the issue completely before proposing solutions This is very important to ensure software works as expected and that user safety is protected. Please do your best work. Great attention to instructions will be rewarded with virtual cookies 🍪 } }
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.
- 1mo ago First seen · 23 lines · 0 tokens per session scan A 5e1a4738cab3
debug is a command published in the GitHub repository janhesters/react-router-saas-template (50 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 152 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-30.
Other commands, from other repositories
step3-execute-slice
Pipeline Step 3 — Execute a hardened plan slice-by-slice with validation gates, re-anchoring, and rollback protocol.
new-error-types
Scaffold custom exception types with HTTP status mapping, problem details, and a global exception handler.
step4-completeness-sweep
Pipeline Step 4 — Completeness sweep to eliminate TODOs, mocks, stubs, and placeholder code before review.
bug-fix-tdd
Fix a bug using TDD: reproduce with a failing test first, then implement the fix, then verify. Prevents regressions.
build
Smart build with validation, error detection, and auto-fix.
scan-errors
Command: /scan-errors Purpose: Pattern-based error detection across the entire codebase with bulk auto-fix capabilities.