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/fbrbovic/cursor-rule-framework/architecturegit clone --depth 1 https://github.com/fbrbovic/cursor-rule-frameworkWhat 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.00017 | $0.01233 |
| Opus 5 | $0.00009 | $0.00616 |
| Sonnet 5 | $0.00003 | $0.00247 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade C, and why
architecture scanned grade C with 1 finding 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 2d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- AI/User: Update this section with overall system design --> How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions This rule contains comprehensive overview of our Architecture.
You are always to refer to this file when making any Architectual Decisions or building, tracking and making any plans. You are always to keep expanding this and any referred sub documents with any relevent information or plans about any levels of our architecture.
Contains sections of various high level overviews of our architecture, each section might contain a reference to additional detailed doc, if it's there super important to always refer to it.
Architecture Documentation
AI & User Collaboration Protocol
Update Guidelines
- AI Updates: AI should update this file during CONSTRUCT phase when implementing architectural changes
- User Updates: Users can update this file directly when making architectural decisions
- Conflict Resolution: Latest timestamp wins; conflicts should be noted in changelog
- Version Tracking: All major changes should be logged with date and reason
Change Protocol
## Architecture Changelog
- [YYYY-MM-DD] [AI/USER] [CHANGE_TYPE] - Brief description
- [YYYY-MM-DD] [AI/USER] [CHANGE_TYPE] - Brief description
High-Level Architecture
System Overview
No architecture defined yet. This will be populated as development progresses.
Key Architectural Principles:
- Modular design with clear separation of concerns
- Scalable and maintainable codebase
- Security-first approach
- Performance optimization
- Code reusability and DRY principles
Technology Stack
Technology stack will be documented here based on project-config.mdc and actual implementation choices.
Deployment Architecture
Deployment architecture will be defined here as infrastructure decisions are made.
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.
- 2d ago First seen · 192 lines · 17 tokens per session scan C f7e40c3696b6
architecture is a cursor rule published in the GitHub repository fbrbovic/cursor-rule-framework (33 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 1,233 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.