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/gradegit 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/grade)<a href="https://agentmods.dev/commands/manavarya09/design-extract/grade"><img src="https://agentmods.dev/badge/commands/manavarya09/design-extract/grade.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.00035 | $0.00297 |
| Opus 5 | $0.00017 | $0.00148 |
| Sonnet 5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
grade 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
Audit the design system at the user-provided URL. Emits a self-contained HTML report card plus JSON + Markdown variants. Pass --badge to also emit a shields.io-style SVG you can drop into any README.
npx designlang grade $ARGUMENTS
If no $ARGUMENTS were supplied, ask the user which URL to grade.
After the run completes:
- Read the generated
*.grade.mdfile from./design-extract-output/ - Surface the headline grade (A–F · score · 8 dimensions)
- Highlight the top 3 strengths and top 3 issues from the report
- Offer to open the HTML in the browser (the
--openflag does this automatically)
If the user wants the live shareable badge URL instead of generating files locally, they can use:
This endpoint is blob-cached 24h with edge caching for ~50ms repeat hits.
Compare two sites with /battle <A> <B>, restyle with /remix, bundle everything with /pack.
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 · 30 lines · 35 tokens per session scan A dee26411477e
grade is a command published in the GitHub repository Manavarya09/design-extract (4,000 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 297 once invoked, about $0.0002 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
full-diagnostic
Comprehensive design system health sweep.
describe-component
Generate an AI-optimised component description.
drift-check
Detect where teams are diverging from the system.
governance-review
Quarterly governance review package.
system-health
Score your design system's overall health.
token-audit
Audit your design token architecture.