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 skills/thewinci/mimirs/debugnpx skills add TheWinci/mimirs --skill debuggit clone --depth 1 https://github.com/TheWinci/mimirsWhat 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.00035 | $0.00312 |
| Opus 5 | $0.00017 | $0.00156 |
| Sonnet 5 | $0.00007 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
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
Goal: find the cause, not just the symptom.
- Locate the symptom —
search "<error text / behavior>"; if you have a name,search_symbols <name>(exact lookup).read_relevantthe suspect code. - Follow the path —
trace from:<entrypoint> to:<suspect>to see how execution reaches the failure (shortest path is highlighted; a dynamic-dispatch hop ends a chain and is reported as such).usages <symbol>for who calls the suspect. - Known issues —
get_annotations(search across notes) — the bug may already be flagged as a caveat. - When introduced —
file_history <file>andsearch_commits "<symptom/area>"to find the change that likely caused it;git_contextfor recent uncommitted edits. - Past attempts —
search_conversation "<symptom>"— was this hit or discussed before? - Fix & record — once fixed,
annotatethe root cause on the file andcreate_checkpointwhat was wrong and how it was resolved.
Finish: state the root cause (file:line), the path from trigger to failure, and the fix.
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 · 18 lines · 35 tokens per session scan A 1288b2551d80
debug is a skill published in the GitHub repository TheWinci/mimirs (29 stars, last pushed 18d ago), licensed Apache-2.0. It adds 35 tokens to every session and 312 once invoked, about $0.0002 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 skills, from other repositories
azure-event-grid-webhooks
Receive and validate Azure Event Grid webhook deliveries. Use when setting up an Event Grid WebHook event handler, implementing the Microsoft.EventGrid.SubscriptionValidationEvent handshake (echo data.validationCode as validationResponse with HTTP 200), implementing the CloudEvents v1.0 HTTP OPTIONS abuse-protection…
baselinker-webhooks
Receive BaseLinker (Base.com) webhooks. Use when building a BaseLinker order or warehouse callback receiver, because BaseLinker is not a normal webhook source: deliveries arrive as HTTP HEAD requests with NO body, the entire payload is in the query string (observed params: orderid, state), there is NO signature…
claude-managed-agents-webhooks
Receive and verify Anthropic Claude Managed Agents (CMA) webhooks. Use when setting up Claude Managed Agents webhook handlers, debugging signature verification, or handling agent session and vault events like session.statusidled, session.statusterminated, session.threadcreated, vault.created, or…
cronofy-webhooks
Receive and verify Cronofy push notifications (webhooks). Use when setting up Cronofy notification channels, debugging Cronofy-HMAC-SHA256 verification, or handling Cronofy calendar events like verification, change, profiledisconnected, conferencingprofiledisconnected, profileinitialsynccompleted, and gdprrequested.…
fireflies-webhooks
Receive and verify Fireflies.ai webhooks. Use when setting up Fireflies webhook handlers, debugging X-Hub-Signature verification, or handling the meeting.transcribed, meeting.summarized, and meeting.botjoined events from Webhooks V2. Also covers the legacy V1 scheme.
gemini-webhooks
Receive and verify Google Gemini API webhooks. Use when setting up Gemini webhook handlers for batch jobs, video generation, or Interactions API function-calling LROs, debugging signature verification, or handling events like batch.succeeded, batch.failed, video.generated, or interaction.completed.