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.5 | $0.00015 | $0.00100 |
| Sonnet 5.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 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
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.
- 1mo 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 4mo ago), licensed MIT. It adds 38 tokens to every session and 251 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
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.
investigate
Investigate a specific issue report with strict, evidence-driven diagnosis.
kimaki-debug
Debug and administer Kimaki itself. Use when sessions do not respond, the bot shows errors, you need the Kimaki or OpenCode service logs, want to profile the bot, restart it (only when asked), connect a model provider with kimaki login, check who may use the bot, or file a Kimaki bug report. ALWAYS load when Kimaki…
horizon-speech
Check that a microphone is usable for Horizon dictation and report which layer is at fault — no signal, bad level, or a genuine model/accent limit. Use when dictation produces wrong, unrelated, or empty text.
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.