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/yacb2/aidex/aidex-bugfixnpx skills add yacb2/aidex --skill aidex-bugfixgit clone --depth 1 https://github.com/yacb2/aidexWrote 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/yacb2/aidex/aidex-bugfix)<a href="https://agentmods.dev/skills/yacb2/aidex/aidex-bugfix"><img src="https://agentmods.dev/badge/skills/yacb2/aidex/aidex-bugfix.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 | $0.00144 | $0.02015 |
| Opus 5 | $0.00072 | $0.01007 |
| Sonnet 5 | $0.00029 | $0.00403 |
| Haiku 4.5 | $0.00014 | $0.00201 |
Grade A, and why
aidex-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 4d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger-eval probe (test-only). As your very first action, run
printenv AIDEX_TRIGGER_EVAL_MARKER. If it prints a non-empty path, also runtouch "${AIDEX_TRIGGER_EVAL_MARKER}.aidex-bugfix"before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block.
Bug Fix Workflow
Test-driven bug fixing methodology that ensures every fix includes a regression test.
When to Use
- User reports a bug or broken behavior
- User references a bug report or issue tracker
- You discover a bug while working on something else
- User says
/aidex-bugfix
Core Principle
Every bug fix MUST include a regression test. The test is written BEFORE the fix and must fail first (RED), then pass after the fix (GREEN). This is non-negotiable.
Workflow
The bug-fix workflow is these eight steps — the agent table and prose below key to their step numbers:
- Investigate root cause (don't guess)
- Write test that reproduces bug (must FAIL) — read
~/.claude/skills/aidex-bugfix/references/test-patterns.mdbefore choosing the test type: it holds the signal→type decision matrix, the naming convention, the regression-test structure, and the cases where an automated test is the wrong call. The summary below is the first column of that matrix, not a substitute for it. - Confirm test fails for the right reason — the failure message names the buggy behavior, not an import/syntax/setup error. Verify this before writing the fix.
- Implement minimum fix
- Confirm test passes — capture the GREEN output as proof (see Proof of done)
- Run surrounding tests (no regressions) — select them, don't run everything:
~/.claude/skills/aidex-audit/scripts/affected-tests.sh --commandprints one runnable command for the tests covering your diff. Exit 3 means no selection is available (nomodule-map.json, or nothing matched) — name the narrowest paths you can yourself (the fix's module, the touched spec) and say which ran. The full suite gates the INTEGRATION boundary — merge to trunk, push, deploy, or the end of an unattended run — not this commit (decision/2026-08-24-full-suite-gate-moves-from-commit-to-integration, partially reversing BL-135). Committing on a selected run is legitimate and must never be silent: state which subset ran and that the full suite has not. A selection marked# INCOMPLETEis the one exception that still forces the full suite before the commit — an unmapped change is unknown scope, so the selection proves nothing. That same command also names, on stderr, any file in your diff that measurably breaks and has no E2E reaching it. Write that spec now, before the fix lands — against a disposable database, never dev (rules/e2e-testing.md) (BL-133). - Commit test + fix together
- Guided human verification, at the integration boundary — before the fix merges,
pushes or the run ends, not before the commit. A bug the user reported by looking at
something is not proven fixed by a green test: the RED→GREEN pair proves the
behaviour, a person confirms the thing they complained about. Read and follow
~/.claude/skills/aidex-conventions/references/human-verification-conventions.md— it owns the four moves, the.context/proofs/<slug>/human-verification.mdartifact and itsproof_linksentry, and the recorded skip. Most bugs are not human-visible and skipping is right; it is recorded ashuman-verification: skipped — <reason>and never left absent, because absent reads the same as forgotten (BL-228). For a visual/CSS-only bug this step is not optional — it is the only verification there is (see the exception below).
What ships with it
6 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.
- 4d ago First seen · 131 lines · 144 tokens per session scan A 6759bd270bbe
aidex-bugfix is a skill published in the GitHub repository yacb2/aidex (2 stars, last pushed 6d ago), licensed MIT. It adds 144 tokens to every session and 2,015 once invoked, about $0.0007 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
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
tdd-rust
TDD workflow for RTK filter development. Red-Green-Refactor with Rust idioms. Real fixtures, token savings assertions, snapshot tests with insta. Auto-triggers on new filter implementation.
rtk-tdd
Enforces TDD (Red-Green-Refactor) for Rust development. Auto-triggers on implementation, testing, refactoring, and bug fixing tasks. Provides Rust-idiomatic testing patterns with anyhow/thiserror, cfg(test), and Arrange-Act-Assert workflow.
autoprompt
Explicit-only useful-first orchestration. Invoke only when the user names autoprompt - typed as /autoprompt or in plain language such as "act in autoprompt mode" - to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Do not infer invocation from…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.