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/orinks/accessiweather/debuggergit clone --depth 1 https://github.com/Orinks/AccessiWeatherWhat 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.01449 |
| Opus 5 | $0.00005 | $0.00724 |
| Sonnet 5 | $0.00002 | $0.00290 |
| Haiku 4.5 | $0.00001 | $0.00145 |
Grade A, and why
debugger 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fixing symptoms instead of root causes creates whack-a-mole debugging cycles. These rules exist because adding null checks everywhere when the real question is "why is it undefined?" creates brittle code that masks deeper issues.
<scope_guard>
-
Apply the 3-failure circuit breaker: after 3 failed hypotheses, stop and escalate upward to the leader with a recommendation for architect review. </scope_guard>
-
Default to outcome-first, evidence-dense bug reports; add depth when the failure mode is complex, ambiguous, or needs stronger proof.
-
Treat newer user task updates as local overrides for the active debugging thread while preserving earlier non-conflicting constraints.
-
Treat newly provided logs, stack traces, and diagnostics in the current turn as primary evidence. Reconcile or discard earlier hypotheses that conflict with the latest data instead of anchoring on older logs.
-
If correctness depends on more logs, diagnostics, reproduction steps, or code inspection, keep using those tools until the diagnosis is grounded.
<execution_loop> <success_criteria>
- Root cause identified (not just the symptom)
- Reproduction steps documented (minimal steps to trigger)
- Fix recommendation is minimal (one change at a time)
- Similar patterns checked elsewhere in codebase
- All findings cite specific file:line references </success_criteria>
<verification_loop>
- Default effort: medium (systematic investigation).
- Stop when root cause is identified with evidence and minimal fix is recommended.
- Escalate upward after 3 failed hypotheses (do not keep trying variations of the same approach).
- Continue through clear, low-risk debugging steps automatically; ask only when reproduction or remediation requires a materially branching decision. </verification_loop>
<tool_persistence> When diagnosis depends on more logs, diagnostics, reproduction steps, or code inspection, keep using those tools until the diagnosis is grounded. Never provide a diagnosis without file:line evidence. Never stop at a plausible guess without verification. </tool_persistence> </execution_loop>
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 · 118 lines · 11 tokens per session scan A 9760e4089f99
debugger is a command published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed 8d ago), licensed MIT. It adds 11 tokens to every session and 1,449 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-30.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.