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/check)<a href="https://agentmods.dev/rules/steipete/agent-rules/check"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/check/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/check"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/check.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.00293 | $0.00293 |
| Opus 5.5 | $0.00117 | $0.00117 |
| Sonnet 5.5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
check 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:
- check — 100% identical, 0 lines differ
What it actually says
Check
Perform comprehensive code quality and security checks.
Primary Task:
Run npm run check (or project-specific check command) and resolve any resulting errors.
Important:
- DO NOT commit any code during this process
- DO NOT change version numbers
- Focus only on fixing issues identified by checks
Common Checks Include:
- Linting: Code style and syntax errors
- Type Checking: TypeScript/Flow type errors
- Unit Tests: Failing test cases
- Security Scan: Vulnerability detection
- Code Formatting: Style consistency
- Build Verification: Compilation errors
Process:
- Run the check command
- Analyze output for errors and warnings
- Fix issues in priority order:
- Build-breaking errors first
- Test failures
- Linting errors
- Warnings
- Re-run checks after each fix
- Continue until all checks pass
For Different Project Types:
- JavaScript/TypeScript:
npm run checkoryarn check - Python:
black,isort,flake8,mypy - Rust:
cargo check,cargo clippy - Go:
go vet,golint - Swift:
swift-format,swiftlint
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 · 37 lines · 293 tokens per session scan A 9971e41869bf
check is a cursor rule published in the GitHub repository steipete/agent-rules (5,677 stars, last pushed 5mo ago), licensed MIT. It adds 293 tokens to every session, about $0.0012 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
lint-config
OXC and React Doctor config rationale - .oxlintrc.json options, front override, better-tailwindcss rule set, oxfmt class order and Markdown scope.
diagnose
Systematic root cause diagnosis — confidence scoring, investigation budgeting, hypothesis branching.
chaos
Failure injection mode — stress test implementations by simulating failures and hostile conditions.
incident
Production incident response — structured triage with blast radius, rollback criteria, and verification.
analyze
Codebase analysis — complexity, coupling, dead code, tech debt hotspots.
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.