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/hevy_rulesgit 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/hevy_rules)<a href="https://agentmods.dev/rules/andreparmar/hevy-mcp-remote/hevy_rules"><img src="https://agentmods.dev/badge/rules/andreparmar/hevy-mcp-remote/hevy_rules.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.00242 | $0.00242 |
| Opus 5 | $0.00121 | $0.00121 |
| Sonnet 5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
hevy_rules 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.
This is a copy
100% identical to hevy_rules — 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
Cursor Rule: hevy-mcp Integration Test Best Practices
-
Always re-run relevant tests after making any change to a test file.
- This ensures that changes are immediately validated and no regressions are introduced.
-
When fixing or updating integration tests:
- Use the correct method signatures and argument types for SDK/client calls.
- Add or update Zod schema validation for API responses to ensure type safety and contract adherence.
- Remove any debug or console.log statements before finalizing changes, unless explicitly requested otherwise.
-
When adding new tests or updating existing ones:
- Prefer validating response data with Zod schemas that match the expected output structure.
- Ensure all test assertions are meaningful and reflect the actual API contract.
-
If a test fails:
- Add temporary debug output (e.g., console.log) only as needed to diagnose the issue, and remove it once resolved.
- Investigate the actual response structure before updating assertions or schemas.
-
Keep integration tests clean and production-ready:
- No unnecessary debug output.
- All code should be idiomatic, concise, and maintainable.
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 · 242 tokens per session scan A 074da33dfd66
hevy_rules is a cursor rule published in the GitHub repository andreparmar/hevy-mcp-remote (0 stars, last pushed 25d ago), licensed MIT. It adds 242 tokens to every session, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to hevy_rules, 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.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.