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 tmusser/ai-engineering-skills --skill bug-capturegit clone --depth 1 https://github.com/tmusser/ai-engineering-skillsWrote 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/tmusser/ai-engineering-skills/bug-capture)<a href="https://agentmods.dev/skills/tmusser/ai-engineering-skills/bug-capture"><img src="https://agentmods.dev/badge/skills/tmusser/ai-engineering-skills/bug-capture.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.1 | $0.00014 | $0.00244 |
| Opus 5 | $0.00007 | $0.00122 |
| Sonnet 5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
bug-capture 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 8d 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
Bug Capture
Purpose
Preserve discovered bugs as artifacts.
When to use
Use when a bug is found, whether or not it is fixed in the current session.
Inputs
- Observed behavior
- Expected behavior
- Reproduction steps
- Affected files
- Verification command
Workflow
- Create or update
BUGS.md. - Add a bug title.
- Record observed and expected behavior.
- Write reproduction steps.
- List affected files.
- Add hypothesis and status.
- Record verification command.
- Add resolution if fixed.
Outputs
BUGS.mdentry with bug title, observed behavior, expected behavior, reproduction steps, affected files, hypothesis, status, verification command, and resolution if fixed
Stop conditions
- The bug is captured well enough for another session to reproduce.
- The issue is not a bug and should become a decision or task instead.
Anti-patterns
- Leaving bug knowledge trapped in chat history.
- Recording "broken" without reproduction steps.
- Closing a bug without verification evidence.
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.
- 8d ago First seen · 49 lines · 14 tokens per session scan A d27a90f0536f
bug-capture is a skill published in the GitHub repository tmusser/ai-engineering-skills (4 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 244 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-08-31.
Other skills, from other repositories
bug-diagnosis
Use this skill to systematically diagnose the root cause of a bug before attempting a fix. Activates when a bug is reported, a test is failing, or unexpected behavior is observed. Prevents guess-and-check debugging that introduces additional bugs while chasing symptoms.
html-ppt-zhangzara-block-frame
Rescuing a messy startup deck into a board-grade system — the diagnosis, the page grammar, and the rebuilt proof pages. Built as a decision-grade design craft deck for founders, exec presenter.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
doca-dpa-hl-tracer
Use this skill when the user runs docadpahltracer to capture/decode DPA-side traces at the programming-events layer (kernel entry/exit, sync points, comm primitive calls, RDMA WR submission, completion drain) — picking TRACE vs CRIT, tuning the JSON config (file-size limits + filesizelimitpolicy, thread…