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/panozzaj/cursor-rules/rspec-run-after-editgit clone --depth 1 https://github.com/panozzaj/cursor-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/panozzaj/cursor-rules/rspec-run-after-edit)<a href="https://agentmods.dev/rules/panozzaj/cursor-rules/rspec-run-after-edit"><img src="https://agentmods.dev/badge/rules/panozzaj/cursor-rules/rspec-run-after-edit.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.00135 | $0.00135 |
| Opus 5 | $0.00068 | $0.00068 |
| Sonnet 5 | $0.00027 | $0.00027 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
rspec-run-after-edit 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 3d 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
Run RSpec Tests After Edit
When an RSpec file (spec/**/*_spec.rb) is created or edited, run the tests within that file to verify the changes and catch any regressions or errors.
Use a command like:
# Run all tests in the file
./bin/rspec path/to/your_spec.rb
# Run a specific test by line number (useful after adding/modifying one test)
./bin/rspec path/to/your_spec.rb:line_number
Debug and fix any failures that arise before proceeding.
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.
- 3d ago First seen · 21 lines · 135 tokens per session scan A 1f32c4d0bd97
rspec-run-after-edit is a cursor rule published in the GitHub repository panozzaj/cursor-rules (3 stars, last pushed 1y ago), licensed MIT. It adds 135 tokens to every session, about $0.0007 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 cursor rules, from other repositories
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
spec
Shared RSpec conventions for the gem suite.
telegram-bot-tests
Test conventions for Telegram Bot library.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
rule-calling-guide
Comprehensive guide for calling VAN QA rules.