Borrowing it
Nothing to install: this file belongs to davidbuenov/dbv-specs-ops. 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/davidbuenov/dbv-specs-ops/master/AGENTS.mdgit clone --depth 1 https://github.com/davidbuenov/dbv-specs-opsWrote 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/davidbuenov/dbv-specs-ops/agents-md)<a href="https://agentmods.dev/instructions/davidbuenov/dbv-specs-ops/agents-md"><img src="https://agentmods.dev/badge/instructions/davidbuenov/dbv-specs-ops/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/davidbuenov/dbv-specs-ops/agents-md"><img src="https://agentmods.dev/badge/instructions/davidbuenov/dbv-specs-ops/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.00418 | $0.00418 |
| Opus 5.5 | $0.00167 | $0.00167 |
| Sonnet 5.5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
dbv-specs-ops 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 8d 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
AGENTS.md — Project Instructions for AI Coding Agents
This project follows Spec-Driven Development (SDD). Read these files at the start of each session before proposing any code or plan:
| File | Purpose |
|---|---|
project.config.md |
Project identity: name, author, license and file header template |
docs/MASTER_PROMPT.md |
Mandatory workflow, rules and boundaries |
docs/SPECIFICATIONS.md |
Current project requirements |
docs/ARCHITECTURE.md |
Stack and technical decisions |
docs/DESIGN.md |
Visual design system: color tokens, typography, components and philosophy (if it exists) |
memory.md |
Context and Decisions: Qualitative knowledge (ADRs, lessons learned, active context) |
task.md |
Current state + Context Snapshot |
Path note (subfolder isolation): In consumer projects where this framework lives inside the
dbv-specs-ops/subfolder, prefix every path in the table above withdbv-specs-ops/(e.g.dbv-specs-ops/docs/MASTER_PROMPT.md,dbv-specs-ops/task.md). Ifdocs/MASTER_PROMPT.mdexists at the workspace root, you are inside the framework repository itself and the paths are those in the table.
⚠️ Core Rules (Strong Pointer)
Read docs/MASTER_PROMPT.md and follow its workflow strictly. If you detect contradictions between the prompt and project specs, halt and report before proceeding.
All initialization logic (Bootstrap), state checking (Specs Check), lifecycle (Workflow) and coding standards are centrally defined there to avoid cognitive redundancy.
🛠️ SDD Framework created by David Bueno Vallejo — free and open source · dbv-specs-ops
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.
- 8d ago First seen · 25 lines · 418 tokens per session scan A 979f6f698924
dbv-specs-ops AGENTS.md is an instructions file published in the GitHub repository davidbuenov/dbv-specs-ops (29 stars, last pushed 4d ago), licensed MIT. It adds 418 tokens to every session, about $0.0017 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-10-15.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.