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/always-on.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/always-on)<a href="https://agentmods.dev/instructions/loiane/specs-driven-development-spring-angular/always-on"><img src="https://agentmods.dev/badge/instructions/loiane/specs-driven-development-spring-angular/always-on/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/always-on"><img src="https://agentmods.dev/badge/instructions/loiane/specs-driven-development-spring-angular/always-on.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.01193 | $0.01193 |
| Opus 5.5 | $0.00477 | $0.00477 |
| Sonnet 5.5 | $0.00239 | $0.00239 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
specs-driven-development-spring-angular always-on.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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-driven Spring + Angular — always-on guardrails
You are working in a workspace that uses the spec-driven workflow defined in docs/methodology.md. These guardrails apply to every request, regardless of which chatmode is active.
Read these on every session
docs/methodology.md— the seven phases.docs/harness-principles.md— the agent validates its own work.docs/artifact-contract.md—.specs/<feature-id>/file layout.docs/spec-format.md— EARS-lite ACs andQ-NNNopen questions.
Hard rules — phases 1, 2, 3 (spec, spec-review, design + tasks)
- Never invent. No silent default for: DB engine, auth scheme, error envelope, pagination, units, currency, retention, etc.
- When you would otherwise pick a default, write a
Q-NNNline in the active artifact's## Open Questionssection and halt for the user. - Quote source tickets verbatim — never paraphrase requirements.
- AC IDs (
AC-NNN) and task IDs (T-NNN) are stable; never renumber. - For Epic-sized work, produce high-level Epic artifacts first (
03-epic-design.md,03a-epic-roadmap.md) before slice-level03-design.mdand04-tasks.md.
Hard rules — phase 4 (build)
- TDD only. Never edit
src/main/**unless.specs/<active-feature>/.tdd-state.jsonshowsphase: redwith a non-emptyred_failure_excerptfor the active task. - Edit only files listed in the active task's
Files in scope(in04-tasks.md). - Never use
-DskipTests,-Dpit.skip,-Dcheckstyle.skip,-Dspotbugs.skip,--no-verify. - Never delete a test or remove an assertion.
- Never lower a coverage threshold.
- Never add
@Disabledwithout a# DisabledReason: <link>comment on the line above. - For frontend tasks (Angular), follow the same red→green→refactor→simplify discipline and never edit files outside
Files in scope.
Hard rules — phase 6 (validate) and phase 7 (review)
- Never modify production code or tests in these phases.
- A skipped test without
# DisabledReason= error. - A missing report for a configured layer = error.
- Every waiver references an ADR file.
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 · 88 lines · 1,193 tokens per session scan A 780857c00d6c
specs-driven-development-spring-angular always-on.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 1,193 tokens to every session, about $0.0048 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.