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/zenobia000/cursor-agentic-coding-template/cursorrulesgit clone --depth 1 https://github.com/Zenobia000/cursor-agentic-coding-templateWhat 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.00954 | $0.00954 |
| Opus 5 | $0.00477 | $0.00477 |
| Sonnet 5 | $0.00191 | $0.00191 |
| Haiku 4.5 | $0.00095 | $0.00095 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cursorrules — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Agentic Coding Template
System Overview
This project uses the Isolation-Focused Memory Bank System with Custom Slash Commands for phased development workflow.
Core Principle: Memory Bank MUST be created and verified before any operations.
Available Slash Commands
Workflow Commands (Phase Sequence)
/van → /plan → /creative → /implement → /reflect → /archive
| Command | Description |
|---|---|
/van |
Initialize project with Memory Bank creation |
/plan |
Task planning and WBS breakdown |
/creative |
Design decisions and architecture planning |
/implement |
Code implementation with progress tracking |
/reflect |
Task review and retrospective |
/archive |
Documentation and knowledge preservation |
Utility Commands
| Command | Description |
|---|---|
/api-design |
RESTful API design with resource modeling |
/debug |
Systematic debugging with hypothesis testing |
/optimize-performance |
Performance analysis and optimization |
/review-code |
Comprehensive code review |
/task-init |
Initialize new task with goal definition |
/task-next |
Prioritize and select next task |
/write-tests |
Test strategy and implementation |
Memory Bank Structure
memory-bank/
├── tasks.md # Source of truth for all tasks
├── activeContext.md # Current focus and active work
├── progress.md # Implementation status
├── projectbrief.md # Project overview and goals
├── techContext.md # Technology stack and constraints
├── systemPatterns.md # Architecture patterns and decisions
├── runbook.md # Operational procedures
├── creative-*.md # Design decisions (created in /creative)
└── README.md # Memory Bank documentation
If Memory Bank doesn't exist:
- STOP all operations immediately
- Run
/vancommand to initialize - Wait for verification before proceeding
Phase Prerequisites
| Command | Requires | Creates/Updates |
|---|---|---|
/van |
- | tasks.md, activeContext.md |
/plan |
tasks.md, activeContext.md | tasks.md (updated) |
/creative |
tasks.md | creative-*.md, tasks.md |
/implement |
tasks.md, creative-*.md | progress.md, tasks.md |
/reflect |
tasks.md, progress.md | tasks.md (updated) |
/archive |
tasks.md, progress.md | archived docs |
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 · 141 lines · 954 tokens per session scan A 4681e1f0055c
cursorrules is a cursor rule published in the GitHub repository Zenobia000/cursor-agentic-coding-template (30 stars, last pushed 2mo ago), licensed MIT. It adds 954 tokens to every session, about $0.0048 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.