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/loiane/specs-driven-development-spring-angularWrote 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/loiane/specs-driven-development-spring-angular/production-code)<a href="https://agentmods.dev/rules/loiane/specs-driven-development-spring-angular/production-code"><img src="https://agentmods.dev/badge/rules/loiane/specs-driven-development-spring-angular/production-code/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/loiane/specs-driven-development-spring-angular/production-code"><img src="https://agentmods.dev/badge/rules/loiane/specs-driven-development-spring-angular/production-code.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.00333 |
| Opus 5.5 | $0.00000 | $0.00133 |
| Sonnet 5.5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
production-code 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 4d 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
Production code rule
When about to edit any file under src/main/**:
- Read
.specs/<active-feature>/.tdd-state.json. - Verify
tasks[<active-task>].phase == "red"andred_failure_excerptis non-empty AND the file appears infiles_in_scope. - If verification fails, stop and tell the user: "No failing test for task
<task-id>. Invoke/build <task-id>to write the test first."
Apply skills: .windsurf/skills/spring-boot-4-conventions/SKILL.md, archunit-rules/SKILL.md, spring-security-baseline/SKILL.md, clarity-over-cleverness/SKILL.md.
Hard convention: package by feature/domain, not by layer. Top-level packages are bounded contexts (e.g. giftcard, order), each with api (published) and internal (private) sub-packages. Never create top-level controller, service, repository, model, dto, or util packages.
Hard convention: no Lombok in any new code. Use Java records, explicit constructors, and LoggerFactory.getLogger(...) instead of @Data, @Getter, @Setter, @Builder, @RequiredArgsConstructor, @Slf4j, etc.
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.
- 4d ago First seen · 20 lines · 0 tokens per session scan A f85359e37988
production-code is a cursor rule published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 333 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-10-12.
Other cursor rules, from other repositories
e2e_tests
Java SDK End to End Tests.
mockito
This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.
issues-format-imports
Java import order and formatter alignment.
ruby-testing-conventions
Ruby testing conventions with matching spec files and TDD workflow.
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.