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 leifericf/agentic-sdk --skill fix-buggit clone --depth 1 https://github.com/leifericf/agentic-sdkWrote 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/leifericf/agentic-sdk/fix-bug)<a href="https://agentmods.dev/skills/leifericf/agentic-sdk/fix-bug"><img src="https://agentmods.dev/badge/skills/leifericf/agentic-sdk/fix-bug/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/leifericf/agentic-sdk/fix-bug"><img src="https://agentmods.dev/badge/skills/leifericf/agentic-sdk/fix-bug.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.00017 | $0.00794 |
| Opus 5.5 | $0.00007 | $0.00318 |
| Sonnet 5.5 | $0.00003 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
fix-bug 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fix-bug
Role: the single-bug fix. Reproduces the bug, writes the failing test, fixes at the source, verifies, lands one commit.
Prerequisites
~/.agentic-sdk/<project>/project.edn exists with :lanes. A bug report: a wrong
behavior, a crash on a specific input, a failing assertion, or a
description.
Procedure
The discipline, in order. Do not skip steps.
- Reproduce. Reduce to the smallest form that shows the wrong behavior: a single function call, a one-input test, a minimal fixture through the failing path. No fix lands without a confirmed reproducer. "Cannot reproduce" goes back to the reporter with what you tried. Keep reproducer fixtures under the project's test fixtures path and cite it in the regression test.
- Failing test first. Write the regression test in the right
surface via write-tests: pure core to the core test namespace, a
native edge to a round-trip integration test, persistence to a
scratch store. Run it; watch it fail for the expected reason. Commit
it first (
Tests: ...) so history proves fail then pass. - Find the cause, not the symptom. Check the decision index (the ADR store from the descriptor) and the design docs first. Behavior that matches an existing ADR or documented design choice is not a bug; report that back instead of fixing it. Then fix at the source: the pure core function, the native body, the persistence transaction, or the shell wiring. Never a caller-side special case, never a test adjustment. Classify the gap: a real defect (fix here), an upstream platform difference (document at the site), or harness debt (fix the harness).
- Fix smallest-sufficient. If the cause is in another module than expected, follow it and say so. A factoring finding is a valid fix-bug outcome: open it as a forward task, do not silently refactor here.
- Verify. Dispatch one verifier running verify-lanes against the project's lanes (from the descriptor): the cheap tier always. When the fix touched a native edge (any native body or the boundary itself), also a round-trip test that compiles and calls the real native code, and the native formatter on changed source. When the fix touched persistence, a transaction-history test. When the fix touched a computation with tolerance, an assertion that returned values are within tolerance on a known-good fixture.
- Commit. One commit via write-commit:
Category: Imperative subject, single line. The regression test and the fix land as the next commit on the tip, not a branch.
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 First seen · 73 lines · 17 tokens per session scan A f77c0ad582f1
fix-bug is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 794 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
upstream-tracker
Manage upstream issue tracking for this project. Use when the user wants to log a bug or friction point in a vendor package or npm dependency, review open upstream items, resolve a tracked issue, run a trend review, generate the upstream observations section of a sprint retrospective, promote upstream observations to…
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…