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/pueraeternis/agentic-project-template/90-project-localgit clone --depth 1 https://github.com/pueraeternis/agentic-project-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/pueraeternis/agentic-project-template/90-project-local)<a href="https://agentmods.dev/rules/pueraeternis/agentic-project-template/90-project-local"><img src="https://agentmods.dev/badge/rules/pueraeternis/agentic-project-template/90-project-local.svg" alt="Measured on agentmods" 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 | $0.00285 | $0.00285 |
| Opus 5 | $0.00143 | $0.00143 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
90-project-local 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 5d 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
Project-Specific Conventions
This rule adapts the shared engineering framework to this specific repository.
Project-specific engineering decisions are defined in:
docs/project/ENGINEERING.md
Follow that document whenever project-specific conventions are required.
Do not duplicate engineering decisions here.
Purpose
Use this rule to remind the agent that project-specific engineering conventions override generic defaults.
Examples include:
- language version;
- dependency management;
- repository layout;
- runtime technologies;
- testing strategy;
- validation commands;
- coding conventions;
- deployment assumptions.
The authoritative source remains ENGINEERING.md.
When ENGINEERING.md Exists
Treat ENGINEERING.md as authoritative for:
- language and runtime versions;
- package management;
- repository structure;
- project technology stack;
- configuration strategy;
- coding conventions;
- validation workflow;
- operational assumptions.
Do not invent engineering conventions that are not documented.
Local Cursor Guidance
Only place Cursor-specific guidance here when it cannot reasonably belong in the framework.
Examples:
- repository-specific prompting hints;
- preferred repository navigation;
- editor-specific workflow adjustments.
Avoid duplicating framework documentation.
Avoid duplicating project documentation.
General Rule
Framework rules define how engineering is performed.
ENGINEERING.md defines how this project is engineered.
This file only bridges the framework to Cursor.
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.
- 5d ago First seen · 80 lines · 285 tokens per session scan A a40f284b679d
90-project-local is a cursor rule published in the GitHub repository pueraeternis/agentic-project-template (2 stars, last pushed 2mo ago), licensed MIT. It adds 285 tokens to every session, about $0.0014 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-31.
Other cursor rules, from other repositories
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
language-agnostic-patterns
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
fable5-reasoning
Fable 5 reasoning protocols: task interpretation, risk-first decomposition, approach selection, interleaved thinking, hypothesis ledgers, premortems, calibration, and the stuck-strategy ladder. Load for complex, ambiguous, or long-horizon tasks, for debugging strategy, or whenever progress stalls.
cursor-agent-orchestration
Cursor 3.7 orchestration guide: when to plan, when to delegate, nested subagents, multi-environment handoffs, /best-of-n, and Await for long-running branches.