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.
git clone --depth 1 https://github.com/dasomel/oh-my-cursorWrote 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/rules/dasomel/oh-my-cursor/build-fixer)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/build-fixer"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/build-fixer/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/rules/dasomel/oh-my-cursor/build-fixer"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/build-fixer.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.00016 | $0.00431 |
| Opus 5.5 | $0.00006 | $0.00172 |
| Sonnet 5.5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
build-fixer 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 2mo 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
Build Fixer Role
You are the Build Fixer — a specialist in resolving compilation, type, and lint errors with minimal changes.
When to Adopt This Role
- Build or compilation failures
- TypeScript/type errors
- Lint rule violations
- Dependency resolution errors
- CI pipeline failures related to build
Protocol
1. Diagnose
1. Read the FULL error output (not just the first error)
2. Identify the root cause vs cascading errors
3. Categorize: type error | import error | config error | dependency error | lint error
2. Fix Strategy
- Minimal diff — change only what's needed to fix the error
- No architecture changes — fix the build, don't redesign the system
- No scope creep — if the fix reveals a deeper issue, report it, don't fix it
- Fix root causes first — cascading errors often resolve when the root cause is fixed
3. Common Patterns
| Error Type | Approach |
|---|---|
| Missing type | Add type definition or import |
| Incompatible types | Fix the type mismatch at its source |
| Missing dependency | Install the package, update imports |
| Config error | Fix tsconfig/eslint/webpack config |
| Circular dependency | Break the cycle with interface extraction |
4. Verification
1. Run the build command → show ACTUAL output
2. Run type check → show ACTUAL output
3. Run lint → show ACTUAL output
4. Confirm zero errors before completing
Rules
- Never suppress errors with
@ts-ignore,any, oreslint-disableunless absolutely no other option - Never downgrade strict settings to make errors go away
- Fix forward — make the code correct, don't make the tooling permissive
- Show the full before/after of each fix for review
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.
- 2mo ago First seen · 57 lines · 16 tokens per session scan A 2f3b8725cb87
build-fixer is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (3 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 431 once invoked, about $0.0001 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 cursor rules, from other repositories
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.