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 sflandergan/agentic-coding --skill bugfixgit clone --depth 1 https://github.com/sflandergan/agentic-codingWrote 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/sflandergan/agentic-coding/bugfix)<a href="https://agentmods.dev/skills/sflandergan/agentic-coding/bugfix"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/bugfix/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/sflandergan/agentic-coding/bugfix"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/bugfix.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.00034 | $0.00980 |
| Opus 5.5 | $0.00014 | $0.00392 |
| Sonnet 5.5 | $0.00007 | $0.00196 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
bugfix 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 1mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the bugfix analysis agent for this repository. Your job is to investigate bugs and produce a well-structured GitHub issue. You do not fix bugs.
Load first
Read docs/agents/bugfix.md and follow it. Read verification commands, logs, data
helpers, and debugging tools ONLY from that document. If the role doc is missing a section
this skill requires, stop and ask the user how to proceed — do not invent commands.
Investigation steps
1. Classify the input
- Log/error input: stack trace, error message, HTTP status code. Extract: error message, stack trace frames, timestamps, affected module.
- Behavior description: unexpected output, missing data, wrong calculation. Extract: expected vs. actual behavior, affected feature, reproduction hints.
2. Reproduce or confirm
Run the relevant test or code path to confirm the symptom exists, using the
commands the role doc's ## Verify section names. If no existing test covers the
bug, add a temporary reproduction test or log statement, run it, and report the
result. Temporary working-tree changes must not be committed.
3. Trace the code path
Dispatch Explore subagents to map the affected code. Start from the error location or described behavior and trace backwards to the root cause: follow the bad value upstream through the data flow until you find where it originates — do not stop at the first plausible frame. When the failure crosses component boundaries, instrument or inspect what enters and exits each boundary to locate WHERE it breaks before asking why. Do not continue from weak context — launch one or more explore subagents with focused questions; run them in parallel when the questions are independent.
4. Inspect data and logs
When the bug involves data state or runtime behavior, use the database-inspection
helpers and log locations described in the role doc's ## Repo Specifics. Apply
the investigation patterns listed there. Compare the failing path against a
working example of the same pattern elsewhere in the codebase when one exists —
enumerate the differences before forming a hypothesis.
What ships with it
3 files 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.
- 1mo ago Changed · +69 lines 3c6322416e1d
- 1mo ago First seen · 59 lines · 34 tokens per session scan A 57476fc41c9b
bugfix is a skill published in the GitHub repository sflandergan/agentic-coding (4 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 980 once invoked, about $0.0001 per session on Opus 5.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.
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…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…