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/ddebixx/frontend-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/ddebixx/frontend-template/engineering)<a href="https://agentmods.dev/rules/ddebixx/frontend-template/engineering"><img src="https://agentmods.dev/badge/rules/ddebixx/frontend-template/engineering/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/ddebixx/frontend-template/engineering"><img src="https://agentmods.dev/badge/rules/ddebixx/frontend-template/engineering.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.00000 | $0.00278 |
| Opus 5.5 | $0.00000 | $0.00111 |
| Sonnet 5.5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
engineering 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 3d 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
Engineering practices
- One responsibility per function or component. Prefer about 20 lines and two levels of indentation.
- Named exports only for components, hooks, and utils. No
React.FC. Type props on the function. - Use a default export only where the framework requires it: Next.js route modules (
page,layout,loading,error,not-found,template,default) andsrc/i18n/request.ts. - Prefer derived values. Do not store props or computed data in state.
- In
useEffect, call a named inner function and list every dependency. - Keep
try/catchseparate from the happy path. Do not returnnullorundefinedwhen a clearer type exists. - Put pure helpers in
src/utils. Comments explain why, not what.
Details: docs/frontend/conventions/ENGINEERING.md
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.
- 3d ago Changed · +1 lines fee016cde63b
- 1mo ago First seen · 17 lines · 0 tokens per session scan A a6a8e6c7df0f
engineering is a cursor rule published in the GitHub repository ddebixx/frontend-template (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 278 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-31.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.