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 SuperMalow/personal-agent-skills --skill diagnosing-bugsgit clone --depth 1 https://github.com/SuperMalow/personal-agent-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/supermalow/personal-agent-skills/diagnosing-bugs)<a href="https://agentmods.dev/skills/supermalow/personal-agent-skills/diagnosing-bugs"><img src="https://agentmods.dev/badge/skills/supermalow/personal-agent-skills/diagnosing-bugs/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/supermalow/personal-agent-skills/diagnosing-bugs"><img src="https://agentmods.dev/badge/skills/supermalow/personal-agent-skills/diagnosing-bugs.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.00088 | $0.01073 |
| Opus 5 | $0.00044 | $0.00536 |
| Sonnet 5 | $0.00018 | $0.00215 |
| Haiku 4.5 | $0.00009 | $0.00107 |
Grade A, and why
diagnosing-bugs 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 10d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnosing Bugs — Read Only
Determine the root cause and explain it with evidence. End with a proposed fix and regression-test strategy, but do not apply either one.
Non-negotiable boundary
- Treat the project and its environment as read-only.
- Do not create, edit, delete, move, rename, format, or generate files.
- Do not modify source code, tests, fixtures, snapshots, configuration, dependencies, lockfiles, documentation, databases, or external services.
- Do not add logs, breakpoints that persist to disk, feature flags, temporary instrumentation, reproduction scripts, harnesses, or tests.
- Do not run migrations, package installation, write-capable API calls, destructive Git commands, or commands likely to mutate persistent state.
- Do not expose secrets. Configuration inspection may report whether a variable exists, but never print its value.
- If reliable diagnosis requires any write or persistent state change, stop. Explain the exact diagnostic change, its scope, risk, and expected evidence, then wait for explicit user authorization. Authorization to diagnose is not authorization to modify.
- If the user also asks for a fix, finish and report the diagnosis first. Implementation is a separate workflow and requires a separate, explicit go-ahead.
1. Establish the symptom
Restate:
- Expected behavior
- Actual behavior and exact error
- Reproduction conditions
- Affected environment and scope
- Last known good state, if known
Separate observed facts from assumptions. Ask only for information that cannot be obtained through safe, read-only inspection.
2. Inspect safely
Prefer existing evidence and existing feedback loops:
- Existing focused tests or reproduction commands known not to mutate persistent state
- Existing logs, stack traces, metrics, profiler output, HAR files, screenshots, and recordings
- Static code tracing from the symptom back through callers and dependencies
- Read-only debugger or REPL inspection
- Read-only Git history, blame, diff, and bisect analysis
- Existing configuration structure, checking presence only when values may be secret
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.
- 10d ago First seen · 99 lines · 88 tokens per session scan A 55d8b39a269f
diagnosing-bugs is a skill published in the GitHub repository SuperMalow/personal-agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,073 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-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.