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.
npx agentmods add instructions/loiane/specs-driven-development-spring-angular/always-ongit clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angularWhat 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 | $0.01193 | $0.01193 |
| Opus 5 | $0.00596 | $0.00596 |
| Sonnet 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 2d 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.
- 2d 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 (58 stars, last pushed 2mo ago), licensed MIT. It adds 1,193 tokens to every session, about $0.0060 per session on Opus 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
spec-kitty AGENTS.md
AGENTS.md instructions for Priivacy-ai/spec-kitty, covering spec kitty development guidelines, ⚠️ critical: load the project charter first, ⚠️ critical: template source location, ⚠️ critical: use canonical sources, never improvise and ⚠️ critical: git workflow — no direct pushes to origin/main.
featherspec AGENTS.md
Instructions for GregorBiswanger/featherspec, covering featherspec — constitution (spec-driven development), single source of truth (do not duplicate), non-negotiables, progress & state sync (gate) and fast path.
featherspec architecture-map.instructions.md
FeatherSpec architecture-map budget rules (thin loader).
featherspec constitution.instructions.md
FeatherSpec constitution editing rules (thin loader).
featherspec knowledge-records.instructions.md
FeatherSpec knowledge record rules — observation, rationale, provenance (thin loader).
featherspec memory-bank.instructions.md
FeatherSpec Memory Bank writing rules (thin loader).