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/manavarya09/design-extract/gallerygit clone --depth 1 https://github.com/Manavarya09/design-extractWrote 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/manavarya09/design-extract/gallery)<a href="https://agentmods.dev/commands/manavarya09/design-extract/gallery"><img src="https://agentmods.dev/badge/commands/manavarya09/design-extract/gallery.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00384 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
gallery 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 4d 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
Run designlang gallery to turn the fidelity reports you've generated into a
deployable static site. It scans a directory for fidelity.json files (one per
clone), then writes an index grid of score cards plus a permalink page for each
clone — every page embeds the SVG score card and OG/Twitter tags, so a shared
link unfurls the measured number.
npx designlang gallery $ARGUMENTS
If no directory is given it scans ./design-extract-output. Generate the
reports first with /fidelity <original> --clone <clone>.
Outputs (under --out, default ./gallery):
| Path | What it is |
|---|---|
index.html |
the gallery grid, best-score first, with summary stats |
<slug>/index.html |
a clone's permalink page (card + motion table + correction plan) |
<slug>/card.svg |
the shareable score card |
Useful flags via $ARGUMENTS:
| Flag | Effect |
|---|---|
--out <dir> |
where to write the static site |
--title <title> |
gallery heading |
--base-url <url> |
absolute base URL so OG image links resolve when deployed |
Deploy the output folder to any static host (Vercel, Netlify, GitHub Pages).
Pair with /fidelity to keep the gallery fresh.
Full reference: https://github.com/Manavarya09/design-extract#full-cli-reference
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.
- 4d ago First seen · 39 lines · 0 tokens per session scan A 9f2d1c1c55a9
gallery is a command published in the GitHub repository Manavarya09/design-extract (4,000 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 384 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
full-diagnostic
Comprehensive design system health sweep.
release-check
Pre-release validation pipeline for a component.
describe-component
Generate an AI-optimised component description.
docs-coverage
Audit whether your documentation surface keeps pace with your components.
drift-check
Detect where teams are diverging from the system.
governance-review
Quarterly governance review package.