Borrowing it
Nothing to install: this file belongs to VoytechG/spec-driven-development. 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/VoytechG/spec-driven-development/main/AGENTS.mdgit clone --depth 1 https://github.com/VoytechG/spec-driven-developmentWrote 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/voytechg/spec-driven-development/agents-md)<a href="https://agentmods.dev/instructions/voytechg/spec-driven-development/agents-md"><img src="https://agentmods.dev/badge/instructions/voytechg/spec-driven-development/agents-md/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/voytechg/spec-driven-development/agents-md"><img src="https://agentmods.dev/badge/instructions/voytechg/spec-driven-development/agents-md.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.00529 | $0.00529 |
| Opus 5.5 | $0.00212 | $0.00212 |
| Sonnet 5.5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
spec-driven-development AGENTS.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 1mo 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-driven-development — Contributor Notes
These notes apply to anyone (human or agent) editing this plugin repo. They do not apply to projects that consume the plugin.
Scope
The plugin is generic. It must contain no references to specific projects, products, codebases, employers, or domains. The only allowed exceptions are inside docs/specs/ design notes, which are historical context.
What the plugin ships
- Five skills:
using-spec-driven-development,load-project-context,maintain-project-docs,review-project-history, andupdate-docs-structure. - Three hooks:
SessionStart,UserPromptSubmit, andStop. - Markdown templates under
templates/. - Three platform manifests: Claude Code, Codex, Gemini CLI.
- One marketplace logo under
assets/.
Every change should leave this list intact unless the change deliberately adds or removes one of these pieces.
Style
- Tight, specific prose. The plugin sells concise documentation; practice it here too.
- No emojis in markdown content.
- Hook scripts:
set -euo pipefail,printf(not heredoc), shellcheck-clean, extensionless filenames. - Skill
SKILL.md: YAML frontmatter withnameanddescriptiononly; imperative-mood body; no padding. - Templates: section headers plus a one-line italic hint per section. No placeholder paragraphs.
Versioning
- Bump
versionin all four manifests together:package.json,.claude-plugin/plugin.json,.claude-plugin/marketplace.json,.codex-plugin/plugin.json,gemini-extension.json. - Add a
RELEASE-NOTES.mdentry per release.
Local checks
bash -n hooks/session-start,bash -n hooks/user-prompt-submit, andbash -n hooks/stopmust pass.- Run
hooks/session-startfrom a throwaway repo withAREAS.mdand from a directory withoutAREAS.md;bash -ndoes not catch every runtime quoting issue. - Run
hooks/user-prompt-submitonce with a project-work prompt and once with a non-project prompt. - Run
hooks/stoponce in a throwaway repo with code-only changes and once after adding a docs change. - JSON manifests must parse.
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.
- 1mo ago First seen · 45 lines · 529 tokens per session scan A dbca5e880e0f
spec-driven-development AGENTS.md is an instructions file published in the GitHub repository VoytechG/spec-driven-development (4 stars, last pushed 5mo ago), licensed MIT. It adds 529 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-31.
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.