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 martineserios/thebrana --skill diagnose-hard-buggit clone --depth 1 https://github.com/martineserios/thebranaWrote 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/martineserios/thebrana/diagnose-hard-bug)<a href="https://agentmods.dev/skills/martineserios/thebrana/diagnose-hard-bug"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/diagnose-hard-bug/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/martineserios/thebrana/diagnose-hard-bug"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/diagnose-hard-bug.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.00017 | $0.00612 |
| Opus 5 | $0.00009 | $0.00306 |
| Sonnet 5 | $0.00003 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
diagnose-hard-bug 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 7d 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
Diagnose Hard Bug (adapter)
ADR-084 vendor+wrap pilot (t-2834). Thin adapter, not a copy — the actual discipline lives in the vendored organ, read fresh every invocation (no state to lose across compaction — steps 1-2 below are the whole procedure):
- Read the vendored skill:
Skill(skill: "diagnosing-bugs")—.claude/skills/diagnosing-bugs/SKILL.md, verbatim upstream, pinnedv1.2.3, tracked inskills-lock.json. Follow its six phases as written. - While following it, remap:
- "Issue tracker" / "issue" / "ticket" → this project's
tasks.json/t-NNNtask. Never prompt for/setup-matt-pocock-skills— not installed, not needed. CONTEXT.md(upstream expects a repo-root glossary file that doesn't exist here) → use this project's own memory instead: the 2-3 most relevantdocs/architecture/*.mdfiles + the task's own context, inline, rather than looking for a file.- Cross-skill references → redirect-check.md, the committed list; re-verify it against the vendored
SKILL.mdon every upstream bump (ADR-084 §1 pump).
- "Issue tracker" / "issue" / "ticket" → this project's
- Early exit (inherited from the vendored skill's own Phase 1): if no tight, red-capable feedback loop can be built, stop and say so explicitly rather than hypothesising — this is a valid, complete exit, not a failure to route around.
- Record on completion or early exit: append one line to
~/.claude/run-state/pocock-diagnosing-bugs.jsonlvia a single shell redirect —printf '%s\n' '{"task_id":...}' >> ~/.claude/run-state/pocock-diagnosing-bugs.jsonl— never read-then-rewrite-the-file; this is a cross-session shared log and a single>>of one line (well underPIPE_BUF) is the only append form safe against two concurrent/brana:fixsessions racing on it. Fields:{"task_id", "phase_reached", "tight_loop_command", "hypotheses_ranked", "outcome", "date"}— the invocation evidence ADR-084 §7's kill/expand evaluation reads.
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.
- 7d ago First seen · 24 lines · 17 tokens per session scan A 46866fadc726
diagnose-hard-bug is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 612 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-09-03.
Other skills, from other repositories
bug-fix-workflow
Structured bug diagnosis and repair workflow using the 5-Whys root cause analysis method. Ensures fixes include tests, documentation, and knowledge capture.
ask-codex
Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate…
root-cause-investigator
Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology. Use when user reports errors, build failures, test failures, performance issues, integration problems, or any "it's not working" scenarios.
create-issue
Transitional alias — prefer /prflow:specs, which runs the same issue-drafting pipeline. Use when a rough user story, bug report, feature idea, piece of feedback, or an implementation plan should be recorded as a GitHub issue rather than built right now. This command name is retained so existing /prflow:create-issue…
retrospective-audit
Stage B of /prflow:retrospective-weekly: given a most-recent-first subset of one recurring pattern's occurrence-PR context bundles (bounded by auditbundlecap), re-derive the root cause and return one JSON object carrying a ranked findings array (one to three sub-patterns) — no edits, no worktree. Invoked as a subagent…
debug
Use when something is broken — a failing or flaky test, crash, wrong result or regression — and the root cause must be reproduced and proven before any fix. On-demand; callable mid-implement. NOT a feature to spec or build (that is specify/implement), NOT the lint/test gate (that is verify), NOT adversarial diff…