dbv-specs-ops: Command for Claude Code

.claude/commands/plan.md

plan is a command for Claude Code from davidbuenov/dbv-specs-ops. It costs 23 tokens per session (170 once invoked), scanned A, original, MIT.

A planning command for the Plan stage of an SDD workflow, which turns an agreed specification into an architecture review and a task breakdown. SDD means developing software through explicit stages such as specification, planning, building, testing, and release.

In plain words
What is it for?
Use it to review a proposed design, split work into tasks, and record the plan in a project file before implementation.
Why use it?
It gives a project a written implementation plan before coding starts and checks the design for architectural risks. It also handles missing specifications by preparing that stage first.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is davidbuenov/dbv-specs-ops's own configuration. It tells Claude Code how to work on dbv-specs-ops itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dbv-specs-ops configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/davidbuenov/dbv-specs-ops/master/.claude/commands/plan.md
Clone the repo
git clone --depth 1 https://github.com/davidbuenov/dbv-specs-ops

Made for: Claude Code.

Wrote 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.

agentmods badge for plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/davidbuenov/dbv-specs-ops/plan.svg)](https://agentmods.dev/commands/davidbuenov/dbv-specs-ops/plan)
Your own site
<a href="https://agentmods.dev/commands/davidbuenov/dbv-specs-ops/plan"><img src="https://agentmods.dev/badge/commands/davidbuenov/dbv-specs-ops/plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 170 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00023 $0.00170
Opus 5 $0.00012 $0.00085
Sonnet 5 $0.00005 $0.00034
Haiku 4.5 $0.00002 $0.00017

Measured 3d ago against content hash 755dacca21a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

plan 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.

.claude/commands/plan.md · 11 lines

What it actually says

Ejecuta ahora la fase Plan (/plan) del ciclo Spec→Plan→Build→Test→Simplify→Ship definido en dbv-specs-ops/docs/MASTER_PROMPT.md (<workflow>, paso 2). Si docs/SPECIFICATIONS.md todavía no tiene contenido real para esta tarea, ejecuta primero la fase Spec en la misma respuesta (no rechaces la petición). Aplica el Adversarial Architect Review y desglosa el trabajo en dbv-specs-ops/task.md (o implementation_plan.md si es complejo), pidiendo aprobación explícita antes de construir.

$ARGUMENTS

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 · 11 lines · 23 tokens per session scan A 755dacca21a6

Subscribe to this mod's changes

plan is a command published in the GitHub repository davidbuenov/dbv-specs-ops (22 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 170 once invoked, about $0.0001 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-09-04.