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 skills add AuraVixStudio/caelo --skill debuggit clone --depth 1 https://github.com/AuraVixStudio/caeloWrote 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/skills/auravixstudio/caelo/debug)<a href="https://agentmods.dev/skills/auravixstudio/caelo/debug"><img src="https://agentmods.dev/badge/skills/auravixstudio/caelo/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/skills/auravixstudio/caelo/debug"><img src="https://agentmods.dev/badge/skills/auravixstudio/caelo/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.00020 | $0.00250 |
| Opus 5.5 | $0.00008 | $0.00100 |
| Sonnet 5.5 | $0.00004 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
Debug (reproduce -> isolate -> fix) 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 (reproduce -> isolate -> fix)
Use this to track down a bug methodically.
Steps
- Reproduce. Get a reliable, minimal repro. If you can't reproduce it, gather the exact error, stack trace, inputs, and environment first.
- Isolate. Narrow the failure: read the stack trace, add targeted logging, bisect the input or the recent changes. Form a hypothesis about the root cause.
- Confirm root cause. Verify the hypothesis — don't fix symptoms. State why it fails.
- Fix. Apply the smallest change that addresses the root cause. Avoid unrelated edits.
- Verify + guard. Re-run the repro to confirm the fix, run the broader tests for regressions, and add a test that would have caught this bug.
Notes
- Resist guess-and-check. One confirmed root cause beats five speculative edits.
- Remove temporary logging/instrumentation before finishing.
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 · 26 lines · 20 tokens per session scan A ea5bd4cdd404
Debug (reproduce -> isolate -> fix) is a skill published in the GitHub repository AuraVixStudio/caelo (25 stars, last pushed 5d ago), licensed Apache-2.0. It adds 20 tokens to every session and 250 once invoked, about $0.0001 per session on Opus 5.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
error-collection
A structured record of confirmed engineering mistakes, their root causes, and checks that prevent them from returning. It uses evidence from real application behavior, not just successful builds.
codebase-explorer
Use when the user asks to understand, map, trace, or locate behavior in an unfamiliar repository. Inspect the actual code, configuration, runtime entrypoints, and tests before proposing changes; stay read-only unless a change is explicitly requested, and report evidence and remaining uncertainty.
flaky-test-triage
Use when a test passes and fails intermittently, behaves differently by order, machine, runtime, timing, or retry, or when the user asks to reduce test flakiness. Gather repeatable evidence, isolate nondeterminism, and repair the causal dependency without weakening test intent.
observability-debugger
Use when the user asks to investigate incidents, errors, latency, crashes, missing events, or anomalous logs and metrics. Correlate real logs, metrics, traces, and runtime state within the authorized scope, redact sensitive data, and separate diagnosis from any restart or remediation.
ci-debugger
A guide for finding the first useful cause of a failed build, test, packaging, deployment, or continuous-integration job. Continuous integration, or CI, automatically checks code in a hosted pipeline.
incident-responder
Use when the user asks to triage, investigate, mitigate, or document a production incident, outage, reliability regression, or security event. Establish scope and safety first, use current evidence, preserve forensic data, distinguish mitigation from root-cause work, and require explicit authorization for…