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/steipete/agent-rulesWrote 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/steipete/agent-rules/bug-fix)<a href="https://agentmods.dev/rules/steipete/agent-rules/bug-fix"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/bug-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/rules/steipete/agent-rules/bug-fix"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/bug-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.00225 | $0.00225 |
| Opus 5.5 | $0.00090 | $0.00090 |
| Sonnet 5.5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
bug-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bug-fix — 100% identical, 0 lines differ
What it actually says
Bug Fix
Streamline bug fixing workflow from issue creation to pull request.
Process:
Before Starting:
- GitHub: Create an issue with a short descriptive title
- Git: Create and checkout a feature branch (
git checkout -b fix/<issue-description>)
Fix the Bug:
- Reproduce the issue
- Write failing test that demonstrates the bug
- Implement the fix
- Verify test passes
- Run full test suite
- Review code changes
On Completion:
- Git: Commit with descriptive message referencing the issue
- Format:
fix: <description> (#<issue-number>)
- Format:
- Git: Push the branch to remote repository
- GitHub: Create PR and link the issue
- Use "Fixes #" in PR description
- Add relevant labels and reviewers
Best Practices:
- Keep changes focused on the specific bug
- Include regression tests
- Update documentation if behavior changes
- Consider edge cases and related issues
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 · 31 lines · 225 tokens per session scan A aca7d844b47e
bug-fix is a cursor rule published in the GitHub repository steipete/agent-rules (5,677 stars, last pushed 5mo ago), licensed MIT. It adds 225 tokens to every session, about $0.0009 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-30.
Other cursor rules, from other repositories
agent
You are a coding agent running on AWS Bedrock AgentCore. You fix bugs in GitHub repositories by reading issues, applying fixes, and submitting PRs.
release
Changesets release pipeline - version PR and its dispatched CI check, shared vX.Y.Z tag, CI gate before tagging, release:check gate, Dependabot changesets, no npm publish, GITHUBTOKEN tag trigger limitation.
ci
CI parity with pnpm run ci, expression-context rules for env blocks, affected vs full graph by event, frozen lockfile, lockfile-keyed store cache, SHA pins, zizmor, deny-by-default permissions.
changesets
Writing changesets - when one is needed, apps-only frontmatter, bump levels for deployed apps, summary style, non-interactive creation.
cd
GitHub Actions CD - called by release.yml after the tag, no push-tags trigger, cf workers versions create then a 100% deployment in deployOrder, scoped API token on the production environment, GitHub-owned deployment record.
lint-config
OXC and React Doctor config rationale - .oxlintrc.json options, front override, better-tailwindcss rule set, oxfmt class order and Markdown scope.