agentmods.dev

markdown-vdb: Command for Claude Code

.claude/commands/execute-prd.md

execute-prd is a command for Claude Code from geckse/markdown-vdb. It costs 0 tokens per session (294 once invoked), scanned A, original, MIT.

A command that implements a feature from a Product Requirements Document (PRD), a written feature specification. It reads the referenced code patterns, follows the listed steps, validates the result, and reports what happened.

In plain words
What is it for?
Use it with a PRD file path to build the specified feature and run its stated validation checks.
Why use it?
It gives implementation a defined sequence and a checklist for checking the finished work. It also highlights anti-patterns the PRD says to avoid.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is geckse/markdown-vdb's own configuration. It tells Claude Code how to work on markdown-vdb 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 markdown-vdb configures →

not rated 29repo 2mo ago A scan 0 tokens original MIT
View source ↗ geckse/markdown-vdb
Reuse

Borrowing it

Nothing to install: this file belongs to geckse/markdown-vdb. 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/geckse/markdown-vdb/main/.claude/commands/execute-prd.md
Clone the repo
git clone --depth 1 https://github.com/geckse/markdown-vdb

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 execute-prd

README.md
[![agentmods](https://agentmods.dev/badge/commands/geckse/markdown-vdb/execute-prd/github.svg)](https://agentmods.dev/commands/geckse/markdown-vdb/execute-prd)
Your own site
<a href="https://agentmods.dev/commands/geckse/markdown-vdb/execute-prd"><img src="https://agentmods.dev/badge/commands/geckse/markdown-vdb/execute-prd/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.

agentmods 80×15 button for execute-prd

Your own site · 80×15
<a href="https://agentmods.dev/commands/geckse/markdown-vdb/execute-prd"><img src="https://agentmods.dev/badge/commands/geckse/markdown-vdb/execute-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 294 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.00000 $0.00294
Opus 5.5 $0.00000 $0.00118
Sonnet 5.5 $0.00000 $0.00059
Haiku 4.5 $0.00000 $0.00029

Measured 2mo ago against content hash 60546e6e4ef3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

execute-prd 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 2mo 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/execute-prd.md · 28 lines

What it actually says

Execute PRD

Implement a feature by following a Product Requirements Document step by step.

PRD path: $ARGUMENTS

Instructions

  1. Read the PRD — Read the file at the path above. Understand the full scope: overview, goals, non-goals, technical design, and implementation steps.

  2. Read referenced files — The PRD's "Patterns to Follow" section references specific codebase files. Read them all to understand the conventions you must match.

  3. Implement step by step — Follow the "Implementation Steps" section in order. For each step:

    • Read the relevant files before modifying them
    • Make the described changes
    • Verify the change works before moving to the next step

  4. Validate — After all steps are complete, work through every item in the "Validation Criteria" checklist:

    • Run any tests mentioned
    • Verify each criterion is satisfied
    • If a criterion fails, fix the issue and re-validate

  5. Check anti-patterns — Review your implementation against the "Anti-Patterns to Avoid" section. Fix any violations.

  6. Report results — Summarize what was implemented, which validation criteria pass, and any issues encountered.

IMPORTANT: You cannot stop until every validation criterion is checked. Do not skip failing tests or claim "all tests pass" if any test has errors in the output.

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. 2mo ago First seen · 28 lines · 0 tokens per session scan A 60546e6e4ef3

Subscribe to this mod's changes

execute-prd is a command published in the GitHub repository geckse/markdown-vdb (29 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 294 tokens. 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.

Planningclifilesystemmarkdownvector-database
Related

execute-prd compared with commands from other repositories

execute-prd next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
execute-prdgeckse/markdown-vdbCommand292mo agoMITA0Claude Code
landing-publishseite-sh/seiteCommand28yesterdayMITA0Claude Code
searchedochi/mdvsCommand2717d agoMITA0Claude Code
infoedochi/mdvsCommand2717d agoMITA0Claude Code
updateedochi/mdvsCommand2717d agoMITA0Claude Code
cleanedochi/mdvsCommand2717d agoMITA0Claude Code
export-jsonschemaedochi/mdvsCommand2717d agoMITA0Claude Code