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 agentmods add rules/rajitsaha/100xprism/fix-bugsgit clone --depth 1 https://github.com/rajitsaha/100xprismWrote 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/rajitsaha/100xprism/fix-bugs)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/fix-bugs"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/fix-bugs.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.01001 |
| Opus 5 | $0.00012 | $0.00500 |
| Sonnet 5 | $0.00005 | $0.00200 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
fix-bugs 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix — Autonomous Bug Fixer
Fix the bug described or linked. Investigate and fix without step-by-step guidance.
Do NOT ask for permission — investigate and fix autonomously.
How to use
/fix— fix the most recent failing CI run/fix <description>— fix from plain description/fix <docker logs paste>— trace error to root cause and fix/fix <Slack URL or paste>— read thread, extract bug report, fix
Phase 1 — Gather context
Read the error in full — message, stack trace, or thread. Do not skip this step.
If the root cause is not obvious from the error/stack/logs → invoke the
systematic-debugging skill first to diagnose before attempting any fix. /fix assumes
you know (or can quickly find) what's broken; for mysterious failures, diagnosis comes
first. Don't guess.
Detect the stack so context-gathering matches the project (canonical block — source:
_lib/reference.md):
PROJECT_ROOT=$(git rev-parse --show-toplevel); cd "$PROJECT_ROOT"
CI_SYSTEM=""; ls "$PROJECT_ROOT"/.github/workflows/*.y*ml >/dev/null 2>&1 && CI_SYSTEM=github-actions
TEST_RUNNER=""
grep -q '"vitest"' package.json */package.json 2>/dev/null && TEST_RUNNER=vitest
[ -z "$TEST_RUNNER" ] && grep -q '"jest"' package.json */package.json 2>/dev/null && TEST_RUNNER=jest
[ -z "$TEST_RUNNER" ] && { [ -f pyproject.toml ] || ls requirements*.txt >/dev/null 2>&1; } && TEST_RUNNER=pytest
[ -z "$TEST_RUNNER" ] && [ -f go.mod ] && TEST_RUNNER="go test"
[ -z "$TEST_RUNNER" ] && [ -f Cargo.toml ] && TEST_RUNNER="cargo test"
# If fixing CI on a GitHub-Actions repo with gh available: read the most recent failure
if [ "$CI_SYSTEM" = github-actions ] && command -v gh >/dev/null 2>&1; then
gh run list --limit 3
gh run view --log-failed "$(gh run list --limit 1 --json databaseId -q '.[0].databaseId')" 2>/dev/null | tail -80
fi
For non-GitHub CI, read the failing job from that provider (GitLab/CircleCI UI or CLI). For docker logs: parse for ERROR/CRITICAL lines, identify service + file. For Slack thread: extract the bug report and reproduction steps.
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.
- yesterday First seen · 103 lines · 23 tokens per session scan A fe58ac197efe
fix-bugs is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 1,001 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-09-03.
Other cursor rules, from other repositories
ops-safety
运维安全规则：系统命令风险说明、回滚方案、Docker/数据库操作安全.
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.