Borrowing it
Nothing to install: this file belongs to loiane/specs-driven-development-spring-angular. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/loiane/specs-driven-development-spring-angular/main/.github/instructions/production-code.instructions.mdgit 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/instructions/loiane/specs-driven-development-spring-angular/production-code)<a href="https://agentmods.dev/instructions/loiane/specs-driven-development-spring-angular/production-code"><img src="https://agentmods.dev/badge/instructions/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/instructions/loiane/specs-driven-development-spring-angular/production-code"><img src="https://agentmods.dev/badge/instructions/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.00521 | $0.00521 |
| Opus 5.5 | $0.00208 | $0.00208 |
| Sonnet 5.5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
specs-driven-development-spring-angular production-code.instructions.md 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 2mo 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 guardrails
You are about to edit production Java code under src/main/**.
Block: TDD precondition
Before writing or editing any line in src/main/**:
- Read
.specs/<active-feature>/.tdd-state.json. - Confirm
tasks[<active-task>].phase == "red"ANDred_failure_excerptis non-empty. - Confirm the file path you are about to edit appears in
tasks[<active-task>].files_in_scope.
If any check fails, refuse the edit and tell the user:
"Cannot edit production code: no failing test for task
<task-id>. Run/build <task-id>so the test-engineer writes the failing test first."
Spring Boot 4 conventions
Follow shared/skills/spring-boot-4-conventions/SKILL.md:
- Constructor injection only.
- Package by feature/domain, not by layer. Top-level packages are bounded contexts (
giftcard,order, …), each withapi(published) andinternal(private) sub-packages. No top-levelcontroller/service/repository/modelpackages. @HttpExchange/RestClient(neverRestTemplatein new code).- Records for DTOs.
@RestControllerAdvicefor error mapping.- Pagination on every list endpoint.
@ConfigurationPropertiesrecords for grouped settings.- No Lombok. No
@Data,@Getter,@Setter,@Builder,@RequiredArgsConstructor,@Slf4j, etc. Java records and explicit constructors replace them.
Architecture conventions
Follow shared/skills/archunit-rules/SKILL.md:
- Each top-level package is a module; cross-module access goes through its
apisub-package only. - Never
importfrom another module'sinternalpackage — enforced by ArchUnit. - No cycles between top-level packages.
Security baseline
Follow shared/skills/spring-security-baseline/SKILL.md:
- Default-deny in
SecurityFilterChain. - Bean Validation on DTOs + service-layer invariant checks.
- Mask PII / secrets in logs.
- No
@CrossOrigin("*")on state-changing endpoints.
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.
- 2mo ago First seen · 51 lines · 521 tokens per session scan A 575c7d050bf2
specs-driven-development-spring-angular production-code.instructions.md is an instructions file published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 17d ago), licensed MIT. It adds 521 tokens to every session, about $0.0021 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.