rspec-run-after-edit

rspec-run-after-edit is a cursor rule for Cursor from panozzaj/cursor-rules. It costs 135 tokens per session, scanned A, original, MIT.

A rule to run the relevant RSpec tests after creating or editing a Ruby test file.

In plain words
What is it for?
It is for running one test file or a specific test by line number, then debugging and fixing failures before continuing.
Why use it?
It catches failures and regressions while the changed test is still fresh.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./bin/rspec path/to/your_spec.rb.

Good fit It is for running one test file or a specific test by line number, then debugging and fixing failures before continuing.

Compare 6 cursor rules from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/panozzaj/cursor-rules
agentmods
npx agentmods add rules/panozzaj/cursor-rules/rspec-run-after-edit

Made for: Cursor.

Wrote 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.

agentmods badge for rspec-run-after-edit

README.md
[![agentmods](https://agentmods.dev/badge/rules/panozzaj/cursor-rules/rspec-run-after-edit/github.svg)](https://agentmods.dev/rules/panozzaj/cursor-rules/rspec-run-after-edit)
Your own site
<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/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.

agentmods 80×15 button for rspec-run-after-edit

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 135 This file is loaded in full into every session.
When invoked 135 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00135 $0.00135
Opus 5.5 $0.00054 $0.00054
Sonnet 5.5 $0.00027 $0.00027
Haiku 4.5 $0.00014 $0.00014

Measured 1mo ago against content hash 1f32c4d0bd97, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

rules/rspec-run-after-edit.mdc · 21 lines

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.

Changes

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.

  1. 1mo ago First seen · 21 lines · 135 tokens per session scan A 1f32c4d0bd97

Subscribe to this mod's changes

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.0005 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.