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/buildermethods/design-os/export-productgit clone --depth 1 https://github.com/buildermethods/design-osWhat 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.07640 |
| Opus 5 | $0.00000 | $0.03820 |
| Sonnet 5 | $0.00000 | $0.01528 |
| Haiku 4.5 | $0.00000 | $0.00764 |
Grade A, and why
export-product 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.
How it starts
The opening of the file, as written. The whole thing — 1,029 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Export Product
You are helping the user export their complete product design as a handoff package for implementation. This generates all files needed to integrate the UI designs into a real codebase.
Step 1: Check Prerequisites
Verify the minimum requirements exist:
Required:
/product/product-overview.md— Product overview/product/product-roadmap.md— Sections defined- At least one section with screen designs in
src/sections/[section-id]/
Recommended (show warning if missing):
/product/data-shape/data-shape.md— Product entities/product/design-system/colors.json— Color tokens/product/design-system/typography.json— Typography tokenssrc/shell/components/AppShell.tsx— Application shell
If required files are missing:
"To export your product, you need at minimum:
- A product overview (
/product-vision) - A roadmap with sections (
/product-roadmap) - At least one section with screen designs
Please complete these first."
Stop here if required files are missing.
If recommended files are missing, show warnings but continue:
"Note: Some recommended items are missing:
- Product entities — Run
/data-shapefor consistent entity naming - Design tokens — Run
/design-tokensfor consistent styling - Application shell — Run
/design-shellfor navigation structure
You can proceed without these, but they help ensure a complete handoff."
Step 2: Gather Export Information
Read all relevant files:
/product/product-overview.md— Product name, description, features/product/product-roadmap.md— List of sections in order/product/data-shape/data-shape.md(if exists)/product/design-system/colors.json(if exists)/product/design-system/typography.json(if exists)/product/shell/spec.md(if exists)- For each section:
spec.md,data.json,types.ts - List screen design components in
src/sections/andsrc/shell/
Step 3: Create Export Directory Structure
Create the product-plan/ directory with this structure:
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.
- yesterday First seen · 1,029 lines · 0 tokens per session scan A 33d131dcaef7
export-product is a command published in the GitHub repository buildermethods/design-os (1,845 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,640 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.