Agentic-Agile Template is a development methodology and starter template for building software through structured collaboration between people and AI coding agents. Development teams use it to organize backlogs, write detailed specifications, coordinate parallel agent work, govern changes, and measure the process. The catalogue entries encode parts of this methodology as instructions and rules.
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/microsoft/agentic-agile-templateWrote 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/microsoft/agentic-agile-template/windsurfrules)<a href="https://agentmods.dev/rules/microsoft/agentic-agile-template/windsurfrules"><img src="https://agentmods.dev/badge/rules/microsoft/agentic-agile-template/windsurfrules/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/microsoft/agentic-agile-template/windsurfrules"><img src="https://agentmods.dev/badge/rules/microsoft/agentic-agile-template/windsurfrules.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.01384 | $0.01384 |
| Opus 5.5 | $0.00554 | $0.00554 |
| Sonnet 5.5 | $0.00277 | $0.00277 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
windsurfrules 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research note: The official Windsurf rules filename was verified against
community documentation and the Codeium blog — .windsurfrules is the
established convention for the repository root and continues to be supported.
Newer Windsurf versions also introduced a directory-based system at
.windsurf/rules/ where rules are defined as named markdown files with
activation modes (always on, manual, glob, model decision). Verify the
current recommendation in the official documentation at https://docs.windsurf.com/
before deploying, as Windsurf's tooling evolves frequently.
Agent Context — [Your Project Name]
Project Purpose
[Describe your project here]
Architecture
- Primary language: [e.g., TypeScript, Python, Go, Rust]
- Framework/runtime: [e.g., Next.js 14, FastAPI, Go stdlib]
- Key dependencies: [e.g., Prisma + PostgreSQL, Redis for caching]
- Project structure:
project-root/
├── src/ # Application source code
├── tests/ # Test files
├── docs/ # Documentation
└── ...
Coding Conventions
- Formatting: [e.g., Prettier with default config; Black + isort for Python]
- Naming: [e.g., camelCase for variables, PascalCase for classes, SCREAMING_SNAKE for constants]
- Imports: [e.g., absolute imports only; group as stdlib / third-party / local with blank lines between]
- Types: [e.g., strict TypeScript — no implicit
any; type hints required on all public functions] - Comments: [e.g., explain why, not what; JSDoc on all public APIs]
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 Changed · +11 lines · +180 tokens per session 68fc381fcb55
- 3d ago First seen · 138 lines · 1,204 tokens per session scan A 3d3e04106bfb
windsurfrules is a cursor rule published in the GitHub repository microsoft/agentic-agile-template (98 stars, last pushed 2d ago), licensed MIT. It adds 1,384 tokens to every session, about $0.0055 per session on Opus 5.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-10-22.
Other cursor rules, from other repositories
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .