agentmods.dev

spec-driven-development-template sdd-specs.instructions.md

Project rules for managing SDD specification folders, where each numbered feature keeps its requirements, plan, tasks, and history together.

In plain words
What is it for?
They guide updates to specification bundles, acceptance criteria, approvals, task lists, change history, and the index of project specifications.
Why use it?
They keep specifications approved, testable, traceable, and aligned with the technical plan before implementation begins.

Instructions file for GitHub Copilot

15 +1 3d ago A scan 231 tokens original MIT
View the source file juanklagos/spec-driven-development-template
Install

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.

agentmods
npx agentmods add instructions/juanklagos/spec-driven-development-template/sdd-specs
Clone the repo
git clone --depth 1 https://github.com/juanklagos/spec-driven-development-template

Made for: GitHub Copilot.

Per session 231 This file is loaded in full into every session.
When invoked 231 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00231 $0.00231
Opus 5 $0.00115 $0.00115
Sonnet 5 $0.00046 $0.00046
Haiku 4.5 $0.00023 $0.00023

Measured 3d ago against content hash 351d9dd113e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-driven-development-template sdd-specs.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 3d 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.

.github/instructions/sdd-specs.instructions.md · 14 lines

What it actually says

Rules for working inside specs/

  • Every spec is a numbered bundle: spec.md, plan.md, tasks.md, history.md (plus optional research.md, contracts/).
  • spec.md must keep its approval section up to date (status Pendiente/Aprobado, date, approver, evidence). Only the user approves.
  • Write acceptance criteria in EARS form: WHEN [trigger], THE SYSTEM SHALL [observable behavior] (ES: CUANDO ..., EL SISTEMA DEBERÁ ...). No vague words without measurable values.
  • plan.md must stay consistent with spec.md: every requirement covered, nothing out of scope.
  • tasks.md uses checkboxes; include test tasks before implementation tasks.
  • Record every scope/requirement change in history.md with date, and reflect status changes in specs/INDEX.md.
  • Hard stop: no implementation code before the spec is approved and the plan is consistent (./scripts/check-sdd-gate.sh . must pass).
Changes

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.

  1. 3d ago First seen · 14 lines · 231 tokens per session scan A 351d9dd113e2

Subscribe to this mod's changes

spec-driven-development-template sdd-specs.instructions.md is an instructions file published in the GitHub repository juanklagos/spec-driven-development-template (15 stars, last pushed 3d ago), licensed MIT. It adds 231 tokens to every session, about $0.0012 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.

Developer WorkflowPlanningProject managementai-agentsai-developmentgithub-templateproject-templatesoftware-architecture
Related

Other instructions, from other repositories

AIAgentMinder CLAUDE.md

Instructions for lwalden/AIAgentMinder, covering claude.md - project instructions, project identity, current state, git / pr state — verify, don't assume and behavioral rules.

lwalden/AIAgentMinder · 570 tokens

aider-desk AGENTS.md

AGENTS.md instructions for hotovo/aider-desk, covering agents.md, common commands, development, type checking and linting and formatting.

hotovo/aider-desk · 1,725 tokens

neurolink CLAUDE.md

Instructions for juspay/neurolink, covering claude.md, project overview, critical rules, architecture and pattern: factory + registry.

juspay/neurolink · 10,386 tokens

FrameCode-VibeWork AGENTS.md

Instructions for Sistema2D/FrameCode-VibeWork, covering agents.md, instruction order, reading-trigger rule, regression rule and when a plan is required.

Sistema2D/FrameCode-VibeWork · 1,416 tokens

EndiorBot CLAUDE.md

Instructions for Minh-Tam-Solution/EndiorBot, a project described as: Local-first AI agent orchestrator for SDLC workflows — 14 role-based agents, 5 channels, 39 unified commands. Tool-agnostic. MIT.

Minh-Tam-Solution/EndiorBot · 19 tokens

scaffold AGENTS.md

Instructions for howells/scaffold, covering scaffold, what a new project takes from here, generated surfaces - never hand-edit, editing this repo and commands.

howells/scaffold · 711 tokens