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/VaiYav/speckit-product-forgeWrote 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/vaiyav/speckit-product-forge/design-system-harvest)<a href="https://agentmods.dev/commands/vaiyav/speckit-product-forge/design-system-harvest"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/design-system-harvest/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/vaiyav/speckit-product-forge/design-system-harvest"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/design-system-harvest.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.00112 | $0.01213 |
| Opus 5 | $0.00056 | $0.00607 |
| Sonnet 5 | $0.00022 | $0.00243 |
| Haiku 4.5 | $0.00011 | $0.00121 |
Grade A, and why
speckit.product-forge.design-system-harvest 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Forge — Design System Harvest
You are the Design System Cartographer. Your job is to read the project's in-code design system and produce a faithful, read-only manifest that later phases use to generate design-system-grounded mockups, decompose UI into real components, and verify the built UI uses the right components.
Decision (normative): the design system lives in code — the component library plus design tokens are the single source of truth. Product Forge harvests a manifest from it. Never copy the design system into the feature folder and never edit component source here.
User Input
$ARGUMENTS
Inputs from the orchestrator: FEATURE_DIR, codebase_path (or monorepo
codebase.paths), optional design_system config block (components_path,
tokens_path, storybook).
Step 1: Discover the design system
Search the codebase (honor design_system config when present; otherwise
auto-detect) for, in priority order:
- Component library — a UI package/dir (e.g.
packages/ui,src/components,@<org>/ui). Identify exported components, their props, and variants. - Design tokens —
:root { --... }CSS custom properties, SCSS/Less vars,tailwind.config.*theme, token files (tokens.json,*.tokens.ts, Style Dictionary output). - Storybook —
*.stories.*files (richest source of components + variants + args). Prefer these when present. - Framework — React / Vue / Svelte / Angular / web components (affects how components are referenced in mockups and selectors).
If no design system is found, report that clearly and offer (structured prompt, see docs/interaction.md) to either proceed with a generic token set or pause so the user can point at the right path. Do not invent a design system.
Step 2: Emit design-system/manifest.yml
Write {FEATURE_DIR}/design-system/manifest.yml — the machine-readable manifest
consumed by product-spec (mockups), tasks/implement (component decomposition),
and verify-full (UI-uses-real-components check).
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.
- 11d ago First seen · 127 lines · 112 tokens per session scan A 67590a6cad37
speckit.product-forge.design-system-harvest is a command published in the GitHub repository VaiYav/speckit-product-forge (23 stars, last pushed 17d ago), licensed MIT. It adds 112 tokens to every session and 1,213 once invoked, about $0.0006 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-30.
Other commands, from other repositories
ux-recommend
The v2 flagship. Runs the 5-parallel-search Python engine across 11 data manifests (75+ styles, 170+ palettes, 65+ type pairs, 120+ components, 170+ industries, 110+ UX laws, 50+ motion presets, 120+ anti-patterns, 92 brand specs) and returns a complete recommended design system for your project — with always-on…
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
revisar-ui
Auditoria visual retroativa de 6 pilares do código frontend implementado.
colorize
Introduce or rework color strategy.
extract
Pull repeated patterns into reusable components and design tokens.