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 renanflustosa/octo-cluster --skill debuggit clone --depth 1 https://github.com/renanflustosa/octo-clusterWrote 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/renanflustosa/octo-cluster/debug)<a href="https://agentmods.dev/skills/renanflustosa/octo-cluster/debug"><img src="https://agentmods.dev/badge/skills/renanflustosa/octo-cluster/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/renanflustosa/octo-cluster/debug"><img src="https://agentmods.dev/badge/skills/renanflustosa/octo-cluster/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.00018 | $0.00159 |
| Opus 5.5 | $0.00007 | $0.00064 |
| Sonnet 5.5 | $0.00004 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
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
Debug mode. Fix bugs with runtime evidence, not speculation.
Problem: $ARGUMENTS
Gather a reproducible signal (test, logs, grep) before each hypothesis. Then: reproduce -> minimal fix -> scoped re-run. No refactors.
When: flaky test, hung process, permission error, API 500, missing dependency mid-run. When NOT: design questions, refactors, or fixes without a reproducible failure.
Output: root cause (1 line) + fix + proof command, <=30 lines. Skill: systematic-debugging.
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 · 20 lines · 18 tokens per session scan A 416fe6f3c5a0
debug is a skill published in the GitHub repository renanflustosa/octo-cluster (4 stars, last pushed 21d ago), licensed MIT. It adds 18 tokens to every session and 159 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-09-16.
Other skills, from other repositories
firebase-crashlytics
Use when implementing crash reporting, capturing fatal/non-fatal errors, recording isolate/async exceptions, customizing reports, or uploading obfuscated symbols.
flutter-errors
Use when hitting layout errors (RenderFlex overflow, unbounded constraints, RenderBox not laid out), scroll errors, or setState-during-build errors.
debugging-strategies
Apply systematic debugging techniques, profiling tools, and root-cause analysis across codebases and stacks. Use when the user needs to investigate bugs, performance issues, or unexpected behavior.
google-ads
Senior Google Ads, single-account layer: plan, launch, audit, diagnose, scale one account. Search, PMax, Demand Gen, Shopping, AI Max, Smart Bidding, RSA, tCPA/tROAS, tracking/OCI, GAQL and API mechanics. Use for: 'why is CPA up', 'PMax cannibalizing brand', 'structure a Search account', 'which conversion action is…
meta-ads
Senior Meta (FB/IG) ads, clean-marketing layer: plan, structure, audit, diagnose, scale an ad account — ODAX objectives, CBO/ABO, Advantage+ audiences and creative, attribution windows, Pixel/CAPI/EMQ, learning phase, creative fatigue, policy rejections, unit economics, API error codes. Use for: 'why is CPA up', 'ad…
pn-session-retro
Run a blameless retrospective on an agent transcript. Classify mistakes under a 5-code taxonomy, emit a structured report at docs/refs/retros/, and recommend concrete hardening. Use after a session that felt off, before a quarterly audit, or via the /pn-retro command. v1 is manual-only; cross-session pattern counters…