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/instructa/viber3d/story.tplgit clone --depth 1 https://github.com/instructa/viber3dWhat 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.00000 | $0.00282 |
| Opus 5 | $0.00000 | $0.00141 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
story.tpl 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.
What it actually says
Use this template to create a new story for tracking in the docs/stories directory.
User Story: {{ID}} - {{TITLE}}
Status: {{STATUS}}
(Valid values: TODO, IN PROGRESS, DONE)
Description:
As a {{USER_TYPE}}, I want {{FEATURE}} so that {{REASON}}.
Acceptance Criteria:
- {{CRITERION_1}}
- {{CRITERION_2}}
- ...
General Tasks:
- All requirements from the plan are implemented
- Code follows project style guidelines
- Tests are written and passing
- Documentation is updated
- Performance considerations addressed
- Security considerations addressed
- Code has been reviewed
Sub Tasks:
- {{SUB_TASK_1}} - Status: {{SUB_TASK_1_STATUS}}
Estimation: {{ESTIMATION}} story points
(Note: One step is 1 story point, which equals 1 day of work for a senior developer)
Developer Notes:
(Note: Add here important learnings, necessary fixes, all other devs need to know to proceed)
- {{NOTE_1}}
- {{NOTE_2}}
- ...
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 · 46 lines · 0 tokens per session scan A 94348ea15657
story.tpl is a cursor rule published in the GitHub repository instructa/viber3d (623 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 282 tokens. 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
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制，1小时超时.
wize-sprint-status
4-implementation: Sprint Status.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.