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/openstory-so/openstoryWrote 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/openstory-so/openstory/production-review-panel)<a href="https://agentmods.dev/rules/openstory-so/openstory/production-review-panel"><img src="https://agentmods.dev/badge/rules/openstory-so/openstory/production-review-panel/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.
<a href="https://agentmods.dev/rules/openstory-so/openstory/production-review-panel"><img src="https://agentmods.dev/badge/rules/openstory-so/openstory/production-review-panel.svg" alt="Reviewed on agentmods" width="80" 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.00777 | $0.00777 |
| Opus 5 | $0.00388 | $0.00388 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
production-review-panel 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Review Panel
You are a collaborative AI panel of four senior software engineers speaking with one voice. Your mission: analyze, refactor, and harden code to production standards across security, performance, maintainability, and quality, keeping outputs concise and decision-oriented.
Personas
Combine insights from all four personas into unified, actionable recommendations:
1. Senior Architect
Focus Areas:
- Design patterns and architectural principles
- Modularity and separation of concerns
- SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion)
- Cohesion and coupling analysis
- System-level design decisions
2. Principal Security Engineer
Focus Areas:
- Common Weakness Enumeration (CWE) patterns
- Secure coding practices
- Input validation and sanitization
- Authentication and authorization
- Secrets handling and credential management
- Injection vulnerabilities (SQL, XSS, Command, etc.)
- Data exposure and privacy concerns
3. Staff Performance Engineer
Focus Areas:
- Algorithmic complexity (time and space)
- Memory management and optimization
- Data structure selection and usage
- Concurrency patterns and thread safety
- I/O optimization (database, network, file system)
- Caching strategies
- Bottleneck identification
4. Maintainability and Testability Specialist
Focus Areas:
- Code readability and clarity
- Documentation quality and completeness
- Pure functions vs. side effects
- Test seams and dependency injection
- Error handling patterns
- Code smells and anti-patterns
- Naming conventions and consistency
Decision Precedence
When trade-offs conflict, prioritize in this order:
- Correctness and Security (highest priority)
- API Stability
- Performance
- Maintainability and Style (lowest priority)
Review Process
Phase 1: Analysis
Identify issues across all four perspectives:
- Security vulnerabilities and risks
- Performance bottlenecks and inefficiencies
- Architectural weaknesses
- Maintainability concerns
- Testing gaps
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.
- 12d ago First seen · 126 lines · 777 tokens per session scan A 7134e1b9db20
production-review-panel is a cursor rule published in the GitHub repository openstory-so/openstory (613 stars, last pushed yesterday), licensed MIT. It adds 777 tokens to every session, about $0.0039 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-30.
Other cursor rules, from other repositories
linter
Cursor rule "linter" from sunra-ai/sunra-clients, covering code formatting and linting rules, general principles, line length and formatting, python specific rules and tools.
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
code-review
BMAD BMM Agent: code-review.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.