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.
npx agentmods add commands/geckse/markdown-vdb/generate-prdgit clone --depth 1 https://github.com/geckse/markdown-vdbWhat 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 | $0.00000 | $0.00414 |
| Opus 5 | $0.00000 | $0.00207 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
generate-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 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.
What it actually says
Generate PRD
Generate a comprehensive Product Requirements Document for the following feature.
Feature: $ARGUMENTS
Instructions
-
Read the base template — Read
docs/prds/base-template.mdto understand the required PRD structure. Readdocs/prds/example-prd.mdto see the quality bar. -
Research the codebase — Explore the project to understand the existing architecture, conventions, data models, and patterns. Read
CLAUDE.mdfor project context. -
Research externally (if needed) — If the feature involves third-party libraries, APIs, or platforms, search the web for current documentation and best practices.
-
Interview the user — IMPORTANT: You MUST ask clarifying questions before writing the PRD. The goal is to reduce assumptions to near zero. Use the AskUserQuestion tool to ask at least 8-10 questions in batches of 3-4, covering:
- Scope: What is in scope vs explicitly out of scope?
- Users: Who is this for? What is their workflow?
- Behavior: What should happen in edge cases?
- Technical: Are there constraints on implementation approach?
- Data: What data model changes are needed?
- Compatibility: Must this be backward compatible?
- Testing: What validation criteria matter most?
- Priority: Which parts are must-have vs nice-to-have?
- Anti-patterns: What mistakes should be explicitly avoided?
Provide recommended answers based on your research. Wait for responses before asking the next batch. After all questions, ask: "Is there anything else I should know that I haven't asked about?"
-
Generate the PRD — Write the full PRD following the base template structure. Every section must be filled in with specific, actionable content. No placeholders, no vague language.
-
Save — Write the PRD to
docs/prds/<feature-name>.md(kebab-case). Present a summary to the user.
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.
- 3d ago First seen · 31 lines · 0 tokens per session scan A 45212a3619c5
generate-prd is a command published in the GitHub repository geckse/markdown-vdb (23 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 414 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.
Other commands, from other repositories
fieldtheory
Explain and drive the Field Theory CLI — bookmark-sourced seeds, repo-aware possibility runs that score ideas onto a 2x2 grid, and the interconnected .md files they leave behind. Trigger when the user asks about ft, bookmarks, seeds, ft possible (or the older name ft ideas), grids, dots/nodes, or how to turn saved…
wiki-init
Initialize a new LLM Wiki in the current directory. Creates the full directory structure, config, and template files.
check-invariants
Runs only the tree CRDT invariant test battery in outl-core. Faster than /check, focused on what can break sync.
prd-review
Review the active PRD with Codex and stream normalized findings to JSONL.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.