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/kardebadas/claude-plugin/bug-investigatenpx skills add kardebadas/claude-plugin --skill bug-investigategit clone --depth 1 https://github.com/kardebadas/claude-pluginWrote 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/kardebadas/claude-plugin/bug-investigate)<a href="https://agentmods.dev/skills/kardebadas/claude-plugin/bug-investigate"><img src="https://agentmods.dev/badge/skills/kardebadas/claude-plugin/bug-investigate.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.00928 |
| Opus 5 | $0.00042 | $0.00464 |
| Sonnet 5 | $0.00017 | $0.00186 |
| Haiku 4.5 | $0.00008 | $0.00093 |
Grade A, and why
bug-investigate 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 today.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Investigate
Overview
Finds the root cause of a bug and reports it. That is the whole job.
No plan, no fix, no edits. Knowing what is wrong is often the thing that is actually needed — because the fix is obvious once you know, because the decision about whether to fix is someone else's, or because the answer changes what gets built rather than what gets patched.
This is the same investigation superb:bug-fix runs as its first step. The
difference is where it stops. If you already know you want the bug fixed end to
end, use superb:bug-fix and let it carry the result into a plan.
Step 0 — Assemble the report
The investigator needs five things, and the invocation argument usually supplies one or two:
| Field | Example |
|---|---|
| Symptom | "uploads over ~5MB fail silently" |
| Reproduction | the steps, or unknown |
| Error text | stack trace, log line, or none surfaced |
| Affected surface | endpoint, screen, command, job |
| Last known good | a date, a release, a commit, or never worked |
Ask for whatever is missing in one batched question, not five. unknown is a
fine answer and belongs in the brief; a silently empty field is not, because the
investigator will fill it with a guess.
Step 1 — Investigate
Take the first branch that applies:
| Condition | What to do |
|---|---|
A subagent mechanism, and superb:bug-investigator is in your available agent types |
Dispatch superb:bug-investigator with the Step 0 report. |
| A subagent mechanism, but that agent is not listed | Dispatch a general subagent, briefed with the text between the SHARED BRIEF markers in ../bug-fix/references/investigator.md. |
| No subagent mechanism | Follow that same bracketed brief yourself, inline, including its "modify no files" rule. |
Name the agent superb:bug-investigator, with the prefix. A bare
bug-investigator resolves to whatever personal agent happens to exist.
Do not substitute superpowers:systematic-debugging. Its four phases run
through hypothesis-testing and implementation, so it would fix the bug — which
is the one thing this skill is for not doing.
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.
- today First seen · 80 lines · 83 tokens per session scan A 780d454eba1f
bug-investigate is a skill published in the GitHub repository kardebadas/claude-plugin (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 83 tokens to every session and 928 once invoked, about $0.0004 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-05.
Other skills, from other repositories
import
Import a self-contained NeatContext context bundle shared by another person, or reconcile a newer copy of a context already on this machine, leaving the source bundle unchanged. Use only when the user explicitly invokes this skill or asks to import a NeatContext bundle.
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
create
Create a fresh NeatContext context from a user-defined behavioral profile and an existing local knowledge folder. Use only when the user explicitly invokes this skill or asks to create a new context rather than save the current conversation.
extensions
Report which extensions the connected NeatContext context expects, and whether this machine provides them. Use when the user asks what a context can reach, why an extension tool is missing, or how to connect one here.
export
Export a NeatContext context saved from a conversation into a self-contained bundle folder that can be shared or moved to another machine. Use only when the user explicitly invokes this skill or asks to export a NeatContext context.
use
Connect or switch Codex to a local NeatContext Context by name or list number. Use only when the user explicitly invokes this skill, names a context to connect, or agrees to a routing suggestion.