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 fco3lho/unlazier-ai --skill bugfixgit clone --depth 1 https://github.com/fco3lho/unlazier-aiWrote 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/fco3lho/unlazier-ai/bugfix)<a href="https://agentmods.dev/skills/fco3lho/unlazier-ai/bugfix"><img src="https://agentmods.dev/badge/skills/fco3lho/unlazier-ai/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/fco3lho/unlazier-ai/bugfix"><img src="https://agentmods.dev/badge/skills/fco3lho/unlazier-ai/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.00038 | $0.00251 |
| Opus 5 | $0.00019 | $0.00125 |
| Sonnet 5 | $0.00008 | $0.00050 |
| Haiku 4.5 | $0.00004 | $0.00025 |
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 9d 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
Bug Fix Workflow
Follow these steps in order. Do not skip to implementation before reproducing the bug.
Step 1: Reproduce
Write a test that reproduces the bug:
function test_<describes_the_bug>():
// Arrange
input = <value_that_triggers_the_bug>
expected = <correct_output>
// Act
result = function_under_test(input)
// Assert
assert result == expected
Verify: The test fails with the expected error.
Step 2: Implement the Fix
Change the minimum code necessary. Follow Surgical Changes:
- Touch only the lines causing the bug
- Do not improve adjacent code, styles, or comments
- Match existing project style
Step 3: Verify
- The reproduction test passes
- All existing tests still pass (no regressions)
Step 4: Edge Cases
- Check null/empty/boundary cases related to this bug
- Add tests for those too
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.
- 9d ago First seen · 45 lines · 38 tokens per session scan A 82f28d1a67d1
bugfix is a skill published in the GitHub repository fco3lho/unlazier-ai (3 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 251 once invoked, about $0.0002 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
ai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode.
debug
Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction.
md-audit
Read-only code quality audit — scan the current working directory for common issues (bugs, dead code, security hotspots, missing error handling) and return a prioritised findings report. No files are edited. Use when asked to "audit the code", "quick audit", "find issues", "code scan", or "what's wrong with this…
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
ast-grep
Searches and rewrites code by AST shape across 25 languages. Use when the target is a syntax pattern (every call/class/import shaped like X, a codemod, a YAML rule) rather than literal text; for plain strings, comments, or filenames, use rg.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.