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/1024xengineer/bytemind/bug-investigationnpx skills add 1024XEngineer/bytemind --skill bug-investigationgit clone --depth 1 https://github.com/1024XEngineer/bytemindWrote 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/1024xengineer/bytemind/bug-investigation)<a href="https://agentmods.dev/skills/1024xengineer/bytemind/bug-investigation"><img src="https://agentmods.dev/badge/skills/1024xengineer/bytemind/bug-investigation.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.00016 | $0.00136 |
| Opus 5 | $0.00008 | $0.00068 |
| Sonnet 5 | $0.00003 | $0.00027 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
bug-investigation 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 6d 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-investigation
Workflow
- Clarify symptom, expected behavior, and actual behavior.
- Provide a minimal reproducible path.
- Collect evidence (logs, call chain, code location, command outputs).
- State root-cause hypotheses with confidence levels.
- Propose a minimal fix and verification steps.
Output Contract
- Symptom Summary
- Reproduction Steps
- Evidence
- Root Cause Hypothesis
- Fix and Verification Plan
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.
- 6d ago First seen · 25 lines · 16 tokens per session scan A b9b412c7ff1e
bug-investigation is a skill published in the GitHub repository 1024XEngineer/bytemind (43 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 136 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-30.
Other skills, from other repositories
ahk-triage
Triage a bug or unexpected behavior. Deep diagnostic analysis with structured report. No tasks created, no harness tracking.
ahk-ask
Ask a question about this codebase — where is X, does Y exist, how does Z work. Read-only. No tasks created, no harness tracking.
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
memoryprofiler
Skill for AI agents capturing Unity Memory Profiler snapshots (com.unity.memoryprofiler) in a Unity project through the unity-open-mcp MCP server.
refactor
Refactor and optimize [code].
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.