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.
git clone --depth 1 https://github.com/baodq97/open-pluginWrote 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/commands/baodq97/open-plugin/export)<a href="https://agentmods.dev/commands/baodq97/open-plugin/export"><img src="https://agentmods.dev/badge/commands/baodq97/open-plugin/export/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/commands/baodq97/open-plugin/export"><img src="https://agentmods.dev/badge/commands/baodq97/open-plugin/export.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.00012 | $0.00275 |
| Opus 5.5 | $0.00005 | $0.00110 |
| Sonnet 5.5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
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 1mo 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
Export the PRD by triggering the PRD compilation phase.
Instructions
- Read
.design-thinking/state.yamlto get the active workspace - Read
{workspace}/state.yamlto get the current state - Validate: Prototype phase must be
approved- If not approved, report: "Prototype phase must be approved before exporting PRD. Current status: {status}"
- If PRD phase is already
approved, report: "PRD already compiled. Find it at{workspace}/prd.md. Use/design-thinking:handoffto copy it." - Otherwise, set PRD phase to
synthesizingand dispatch the prd-compiler agent:- Pass all required input file paths (resolved)
- Include workspace path
- After prd-compiler returns, dispatch qg-validator for the PRD phase
- 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)
- PASS/WARN: Set status to
- After user approves, update state:
phases.prd.status: approved
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.
- 1mo ago First seen · 23 lines · 12 tokens per session scan A 8015077b0ba8
export is a command published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 275 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
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. check mode writes nothing and reports where the existing docs and the code disagree.
visual-plan
Visual HTML implementation plan for a feature — state machines, code snippets, edge cases.
clean
Turn messy or multi-format CSV exports into one clean, categorized, analysis-ready file.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.