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 derio-net/super-fr --skill fr-debugginggit clone --depth 1 https://github.com/derio-net/super-frWrote 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/derio-net/super-fr/fr-debugging)<a href="https://agentmods.dev/skills/derio-net/super-fr/fr-debugging"><img src="https://agentmods.dev/badge/skills/derio-net/super-fr/fr-debugging/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/derio-net/super-fr/fr-debugging"><img src="https://agentmods.dev/badge/skills/derio-net/super-fr/fr-debugging.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.00134 | $0.01746 |
| Opus 5.5 | $0.00054 | $0.00698 |
| Sonnet 5.5 | $0.00027 | $0.00349 |
| Haiku 4.5 | $0.00013 | $0.00175 |
Grade A, and why
fr-debugging 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 13d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fr-debugging
superpowers:systematic-debugging, wrapped in isolation. The root-cause
investigation, the failing test, and the fix all happen in the isolation
workspace, so the base repo is never touched and the fix lands as a reviewed
PR — the debugging analogue of fr-brainstorming / fr-goal.
Announce at start: "I'm using fr-debugging to find the root cause in isolation."
This skill owns WHERE debugging happens (isolation) and the autonomy contract.
It delegates HOW — the Iron Law, the four phases, the supporting techniques —
to superpowers:systematic-debugging, invoked unchanged.
0. Isolation first — hard gate
Before ANY command — reproduction, evidence-gathering, instrumentation, reads included; "just check X first" never reorders this:
- Already inside an active fr isolation workspace? (e.g. a bug found
mid-fr-goal implementation) — reuse it. The failing test + fix land on
that feature's branch and ride its existing PR; a bug found while building a
feature must not spawn a competing PR. Confirm with
fr isolation status. - Cold start (standalone bug, no active workspace):
Name the branch for the bug now (fr isolation up --branch fix/<slug> [--profile <name>]fix/<slug>); the worktree, PR, and cleanup key off it. A cold-startfix/<slug>is cut from freshly-fetchedorigin/<default>(#322), so the fix is clean of whatever the base checkout is parked on — to debug on the current branch by intent, add--base HEAD. No devcontainer profile → HARD STOP — offer the fr-init interview; there is no unisolated fallback. (Under fr-goal: treat as a blocker — pause, fr-init, resume.)
From here on follow fr-isolation's exec-bridge discipline: read/edit files in
the worktree, run every command through fr isolation exec -- …. A broken
environment is repaired with fr isolation restart, then rebuild (worktree, cursor and
uncommitted work kept), never down --force; a forced down preserves the run record, but the workspace and its uncommitted fix are gone.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago Changed · +1 lines b4774cc8c52a
- 15d ago Changed 8f74820d217c
- 19d ago Changed · -1 lines 92a1fdbb6a3b
- 23d ago Changed · +2 lines 9e0d4ec3f90b
- 24d ago Changed · +2 lines 6794c552b3c5
- 27d ago Changed · +1 lines 6dae01e8fefa
- 1mo ago First seen · 116 lines · 134 tokens per session scan A b3291aeb7946
fr-debugging is a skill published in the GitHub repository derio-net/super-fr (2 stars, last pushed today), licensed MIT. It adds 134 tokens to every session and 1,746 once invoked, about $0.0005 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-31.
Other skills, from other repositories
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
bug-fixer
A bug reproduces, the expected behaviour is clear, and the fix stands apart from the current work.
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
git-investigate
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).