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 soulcodex/agentic --skill fix-buggit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/fix-bug)<a href="https://agentmods.dev/skills/soulcodex/agentic/fix-bug"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/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/soulcodex/agentic/fix-bug"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/fix-bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.00525 |
| Opus 5.5 | $0.00022 | $0.00210 |
| Sonnet 5.5 | $0.00011 | $0.00105 |
| Haiku 4.5 | $0.00005 | $0.00052 |
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.
What it actually says
Fix Bug Skill
Investigate and fix the reported bug systematically.
Step 1 — Understand the Bug
Gather:
- What is the expected behavior?
- What is the actual behavior?
- How is it reproduced? (steps, input, environment)
- Is there an error message, stack trace, or failing test?
If this information is missing, ask the user before proceeding.
Step 2 — Locate the Root Cause
Read the relevant code:
- Start at the reported error location or the code path described in reproduction steps.
- Trace upward through callers to understand context.
- Trace downward through callees to understand what data flows in.
- Look for: off-by-one, null dereference, wrong conditional, missing error handling, incorrect assumption about external behavior, race condition.
State the root cause explicitly before writing any fix:
"Root cause: The
findUserfunction assumes the result is never null, but the database returns null when no row matches. The null propagates touser.emailaccess, causing the crash."
Step 3 — Write a Failing Test First (if no test exists)
Before fixing, write a test that reproduces the bug and currently fails. This proves you understand the bug and prevents regression.
Step 4 — Fix
Apply the minimal fix that addresses the root cause. Do not refactor surrounding code unless it is directly related to the bug.
Step 5 — Verify
Run the test written in Step 3 — it must now pass. Run the full test suite — no regressions introduced.
Step 6 — Summarize
Output:
## Bug Fix Summary
**Root cause**: [One sentence]
**Fix**: [What was changed and why]
**Test added**: [File and test name]
**Regression risk**: [None / Low / Medium — explain if not None]
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 · 75 lines · 54 tokens per session scan A 6cc1c42f6ddf
fix-bug is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 29d ago), licensed MIT. It adds 54 tokens to every session and 525 once invoked, about $0.0002 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
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
issue-resolve
Use when an assessed gflow-cli issue (verdict CONFIRMED-BUG or LIKELY-BUG) has localized, verifiable scope and should be driven to a fix. Mutating and gated: it works in an isolated worktree, fixes test-first, and opens a DRAFT PR for human review. Built to run autonomously (hermes-ops) within a strict action envelope…
test-patterns
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end…
od-code-migration
Default reference pipeline for the code-migration taskKind — code-import → design-extract → token-map → rewrite-plan → patch-edit ↔ build-test devloop → diff-review → handoff.
hatch3r-bug-fix
Step-by-step bug fix workflow. Diagnose root cause, implement minimal fix, write regression test. Use when fixing bugs, working on bug report issues, or when the user mentions a bug.