agentmods.dev

export

A command that compiles a product requirements document from approved Design Thinking materials. It runs a review of the result before presenting it for approval.

In plain words
What is it for?
Use it to create, validate, and review a PRD after prototype approval, with retries when the quality check finds failures.
Why use it?
It ensures the PRD is generated only after the prototype phase is approved and gives the document a quality check before handoff.

Command

4 3mo ago A scan 12 tokens original MIT
View the source file baodq97/open-plugin
Install

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.

agentmods
npx agentmods add commands/baodq97/open-plugin/export
Clone the repo
git clone --depth 1 https://github.com/baodq97/open-plugin
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 275 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00012 $0.00275
Opus 5 $0.00006 $0.00138
Sonnet 5 $0.00002 $0.00055
Haiku 4.5 $0.00001 $0.00028

Measured yesterday against content hash 8015077b0ba8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

export 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 yesterday.

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.

plugins/design-thinking/commands/export.md · 23 lines

What it actually says

Export the PRD by triggering the PRD compilation phase.

Instructions

  1. Read .design-thinking/state.yaml to get the active workspace
  2. Read {workspace}/state.yaml to get the current state
  3. Validate: Prototype phase must be approved
    • If not approved, report: "Prototype phase must be approved before exporting PRD. Current status: {status}"
  4. If PRD phase is already approved, report: "PRD already compiled. Find it at {workspace}/prd.md. Use /design-thinking:handoff to copy it."
  5. Otherwise, set PRD phase to synthesizing and dispatch the prd-compiler agent:
    • Pass all required input file paths (resolved)
    • Include workspace path
  6. After prd-compiler returns, dispatch qg-validator for the PRD phase
  7. Route on QG verdict:
    • PASS/WARN: Set status to review_pending, present PRD to user for review
    • FAIL: Re-dispatch prd-compiler with QG feedback (max 3 retries)
  8. After user approves, update state: phases.prd.status: approved
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. yesterday First seen · 23 lines · 12 tokens per session scan A 8015077b0ba8

Subscribe to this mod's changes

export is a command published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 275 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-08-31.

Code reviewDocumentsPlanningclaude-codeclaude-code-marketplaceclaude-code-plugins
Related

Other commands, from other repositories

security-audit-static

Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.

phuryn/pm-skills · 29 tokens

performance-audit-static

Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.

phuryn/pm-skills · 33 tokens

sprint

Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.

phuryn/pm-skills · 15 tokens

document-app

Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.

phuryn/pm-skills · 44 tokens

analyze-test

Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.

phuryn/pm-skills · 20 tokens

plan-okrs

Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.

phuryn/pm-skills · 17 tokens