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/frontend-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/frontend-code)<a href="https://agentmods.dev/instructions/loiane/specs-driven-development-spring-angular/frontend-code"><img src="https://agentmods.dev/badge/instructions/loiane/specs-driven-development-spring-angular/frontend-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/frontend-code"><img src="https://agentmods.dev/badge/instructions/loiane/specs-driven-development-spring-angular/frontend-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.00255 | $0.00255 |
| Opus 5.5 | $0.00102 | $0.00102 |
| Sonnet 5.5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
specs-driven-development-spring-angular frontend-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
Frontend code guardrails (Angular)
These rules apply when a task includes files under src/**.
Build-phase rules (TDD)
- Test-first: write/extend failing tests before implementing behavior.
- Edit only files listed in the active task's
Files in scope. - Never skip frontend tests to force green.
- Never remove assertions from existing tests.
Angular implementation rules
- Prefer standalone components and typed interfaces/models.
- Keep smart/container logic separate from presentational components where practical.
- Avoid hardcoded API URLs in components; route all calls through services.
- Keep templates accessible: semantic buttons/inputs, labels, and keyboard-operable controls.
Test rules
- Add/maintain component/service tests for new behavior.
- Every user-input validation rule needs a negative-path test.
- For optimistic-update flows, test both success and rollback paths.
Validate/review rules
- During
/validateand/review, never modify production code or tests. - Missing frontend validation outputs (lint/test/build for changed UI scope) is an error.
- Any waiver must reference an ADR.
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 · 35 lines · 255 tokens per session scan A 66597779a0e9
specs-driven-development-spring-angular frontend-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 255 tokens to every session, about $0.0010 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
vibetags com-example-service-NewAnnotationsShowcase-SandboxTestHelper.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for sandboxtesthelper and sandbox restriction.
vibetags com-example-testing-PaymentFixturesTest.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for paymentfixturestest and context & focus.
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.