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/andreparmar/hevy-mcp-remote/rerun-tests-when-changesgit clone --depth 1 https://github.com/andreparmar/hevy-mcp-remoteWrote 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/andreparmar/hevy-mcp-remote/rerun-tests-when-changes)<a href="https://agentmods.dev/rules/andreparmar/hevy-mcp-remote/rerun-tests-when-changes"><img src="https://agentmods.dev/badge/rules/andreparmar/hevy-mcp-remote/rerun-tests-when-changes.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.00041 | $0.00041 |
| Opus 5 | $0.00020 | $0.00020 |
| Sonnet 5 | $0.00008 | $0.00008 |
| Haiku 4.5 | $0.00004 | $0.00004 |
Grade A, and why
rerun-tests-when-changes 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 4d 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.
This is a copy
100% identical to rerun-tests-when-changes — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Make sure to re-run tests whenever you make a change to the the source code and also ensure that the test cases are up to date
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.
- 4d ago First seen · 6 lines · 41 tokens per session scan A 5e8849e0ad7c
rerun-tests-when-changes is a cursor rule published in the GitHub repository andreparmar/hevy-mcp-remote (0 stars, last pushed 25d ago), licensed MIT. It adds 41 tokens to every session, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to rerun-tests-when-changes, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.