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/stunt-double/stuntdouble-mcpWrote 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/stunt-double/stuntdouble-mcp/review-checklist)<a href="https://agentmods.dev/rules/stunt-double/stuntdouble-mcp/review-checklist"><img src="https://agentmods.dev/badge/rules/stunt-double/stuntdouble-mcp/review-checklist.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.1 | $0.00000 | $0.00197 |
| Opus 5 | $0.00000 | $0.00098 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
review-checklist 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 8d 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
review-checklist:
Before merging:
- Run relevant Stunt Double checklists against staging before merging UX changes.
- Verify that existing workflows still pass after modifying user-facing flows.
- Check Stunt Double feedback (
list_feedback) for regressions related to the changed area.
Coverage:
- Ensure new user journeys have corresponding workflows or checklist items for ongoing validation.
- If a new user-facing feature is added, check that at least one actor persona covers the target user type.
- If no actor exists for the affected user segment, recommend creating one via
create_actor.
After merging:
- Re-run affected workflows against the deployed environment to confirm the fix.
- Update feedback status to "resolved" for any issues addressed by the change.
- Review workflow run history (
get_workflow, which returnsrecent_runs) to confirm no regressions.
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.
- 8d ago First seen · 24 lines · 0 tokens per session scan A 0bc52280016b
review-checklist is a cursor rule published in the GitHub repository stunt-double/stuntdouble-mcp (1 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 197 tokens. 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
react-chakra-ui-cursorrules-prompt-file
Cursor rules for React development with Chakra UI integration.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.
beefreeSDK-nocode-content-editor-cursorrules-prompt-file
Cursor rules for embedding Beefree SDK's no-code content editors (for emails, pages, and popups) into a web application.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.
cursor-mcp-optimization
Cursor 3.7 MCP optimization: browser Design Mode, canvases, Figma, Cloudflare tools, MCP Apps structured content, and direct action patterns.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.