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/synaptiai/prompt-decoratorsWrote 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/synaptiai/prompt-decorators/903-story-template)<a href="https://agentmods.dev/rules/synaptiai/prompt-decorators/903-story-template"><img src="https://agentmods.dev/badge/rules/synaptiai/prompt-decorators/903-story-template/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/synaptiai/prompt-decorators/903-story-template"><img src="https://agentmods.dev/badge/rules/synaptiai/prompt-decorators/903-story-template.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.00828 | $0.00828 |
| Opus 5 | $0.00414 | $0.00414 |
| Sonnet 5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
903-story-template 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 11d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Template Standards
1.0.0
Requirements
- Follow standardized story structure
- Include all required sections
- Track progress accurately
- Maintain implementation history
- Stories must be organized under Epic directories
File Structure
Stories must be placed in their Epic's directory:
.ai/epic-{n}/story-{m}.story.md
Story Structure
Required Sections
1. Header
Epic-{N}: {Epic Title} Story-{M}: {Story Title}
2. Story Description
As a {role} I want {action} so that {benefit}
3. Status
- Draft
- In Progress
- Complete
- Cancelled
4. Context
- Background information
- Current state
- Story justification
- Technical context
- Business drivers
- Relevant history from previous stories
5. Estimation
Story Points: {Story Points (1 SP = 1 day of Human Development = 10 minutes of AI development)}
6. Tasks
Task Groups
-
- {Major Task Group 1}
-
- {Test Subtasks (as needed)}
-
- {Subtask}
Note:
- Use - [x] for completed items
- Use
skipped/cancelled items - Follow TDD - Start with Writing Tests Subtask
7. Additional Sections
Constraints
- List any technical or business constraints
Data Models / Schema
- Database schemas
- API request/response models
- Interfaces/types
Structure
- Module organization
- File structure plan
Diagrams
- Mermaid diagrams as needed
Dev Notes
- Implementation commentary
- Important considerations
- Technical decisions
Chat Command Log
- Commands from User
- Agent Question and Users Response
Examples
Story
As a chess player I want to see a clear and interactive chessboard so that I can play chess in the web browser
Status
In Progress
Context
Part of Epic-1 which implements the core 2-player chess game. This story focuses on the visual and interactive aspects of the chessboard. The project setup (Story-1) is complete, providing the foundation for UI implementation.
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.
- 11d ago First seen · 157 lines · 828 tokens per session scan A 63ce82a9b768
903-story-template is a cursor rule published in the GitHub repository synaptiai/prompt-decorators (43 stars, last pushed 3d ago), licensed Apache-2.0. It adds 828 tokens to every session, about $0.0041 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
client-workflow-bootstrap
Cursor rule "client-workflow-bootstrap" from ulises-jeremias/agent-toolkit, covering agent vs skill rule — why agent (cite clause), when to use vs holistic, caller / skills / handoff, interview process and gate before generating.
task-tracking-basic
Basic task tracking for Level 2 Simple Enhancement tasks.
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.
cli-error-handling
CLI command error handling patterns.