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 mrzhangguoguo/oh-my-workbuddy --skill build-fixgit clone --depth 1 https://github.com/mrzhangguoguo/oh-my-workbuddyWrote 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/mrzhangguoguo/oh-my-workbuddy/build-fix)<a href="https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/build-fix"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/build-fix/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/mrzhangguoguo/oh-my-workbuddy/build-fix"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/build-fix.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.00025 | $0.00235 |
| Opus 5 | $0.00013 | $0.00118 |
| Sonnet 5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
build-fix 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 11d 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
Ported from oh-my-codex
build-fix. OMX runtime conventions ($macroinvocation,omxCLI,.omx/state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list,.workbuddy/memory).
Build Fix — deprecated
Hard-deprecated. Do not invoke or route this skill.
Build failures should be handled by the active execution, debugging, or verification
workflow (e.g. run the build, read the error, fix the offending code, re-run). There is
no separate persistent "build-fix" mode in WorkBuddy — repair happens inline as part of
normal task progress, tracked with the task list and .workbuddy/memory.
If you arrived here from an old reference, just fix the build directly in the current session.
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.
- 11d ago First seen · 23 lines · 25 tokens per session scan A 7b4e9a675cd8
build-fix is a skill published in the GitHub repository mrzhangguoguo/oh-my-workbuddy (2 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 235 once invoked, about $0.0001 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
Build Tool Conventions
Maven/Gradle standard layout, dependency management, plugin versioning, and reproducible builds.
rag-and-memory
Patterns for Retrieval-Augmented Generation (RAG) and agent memory systems. Retrieves only relevant context, prevents context bloat, and maintains coherent state across sessions.
simplicity-first
Prevents overengineering by enforcing minimum viable code. No speculative features, no premature abstractions, no unnecessary complexity.
surgical-changes
Enforces minimal code modifications — touch only what you must. Prevents drive-by refactoring, comment deletions, and style changes unrelated to the task.
api-design
Design stable, versioned, self-documenting APIs. Easy to use correctly, hard to use incorrectly. Apply Hyrum's Law from day one.
frontend-engineering
Accessible, performant, responsive UI patterns. Component design, state management discipline, and Core Web Vitals compliance.