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/daffy0208/ai-dev-standards/cursorrulesgit clone --depth 1 https://github.com/daffy0208/ai-dev-standardsWhat 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.04018 | $0.04018 |
| Opus 5 | $0.02009 | $0.02009 |
| Sonnet 5 | $0.00804 | $0.00804 |
| Haiku 4.5 | $0.00402 | $0.00402 |
Grade A, and why
cursorrules 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 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.
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 — 584 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Assistant Rules for ai-dev-standards
Project Overview
This is the AI Dev Standards repository - a complete system for maintaining AI development standards with automatic installation and syncing.
Key Components:
- skills/ - 64 specialized skills (mvp-builder, rag-implementer, data-visualizer, etc.)
- mcp-servers/ - 50 MCP server implementations (executable tools)
- tools/ - 9 LangChain/CrewAI tools + 4 supporting scripts
- components/ - 13 reusable React components and patterns
- integrations/ - 6 third-party service integrations (OpenAI, Supabase, etc.)
- templates/ - Config file templates (.cursorrules, .gitignore, etc.)
- CLI/ - Command-line tool for automatic installation and syncing
- installers/bootstrap/ - Auto-bootstrap system (
npx @ai-dev-standards/bootstrap) - docs/ - Complete documentation (2500+ lines)
Current Status: ✅ Production Ready (v1.3.0) Coverage: 92% skill-to-MCP parity (1.1:1 ratio) • 107 total resources
Critical: Load Context First
Before performing ANY task in this repository or in projects referencing it:
- ✅ Check if
ai-dev-standards/is accessible - ✅ Read
meta/PROJECT-CONTEXT.md(understand the system) - ✅ Read
meta/HOW-TO-USE.md(learn navigation) - ✅ Review
meta/DECISION-FRAMEWORK.md(when making technology choices) - ✅ Review
docs/SYSTEM-OVERVIEW.md(understand the complete architecture)
Time investment: 3-5 minutes Value: Prevents mistakes, enables effective use, ensures consistency
Core Principles
1. Check Before Creating
ALWAYS search for existing solutions before building new:
- Search
meta/skill-registry.jsonfor relevant skills - Check
standards/architecture-patterns/for design approaches - Review
playbooks/for operational procedures - Look in
components/for reusable implementations - Consult
examples/for reference code
Never invent when a standard exists.
2. Follow Standards Always
ALL code must follow:
- Conventions in
standards/coding-conventions/(when created) - Best practices in
standards/best-practices/ - Patterns in
standards/architecture-patterns/ - Security guidelines (never compromise)
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 · 584 lines · 4,018 tokens per session scan A 9472e11ffdfe
cursorrules is a cursor rule published in the GitHub repository daffy0208/ai-dev-standards (36 stars, last pushed 8mo ago), licensed MIT. It adds 4,018 tokens to every session, about $0.0201 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
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.