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/geo-mena/distill/covergit clone --depth 1 https://github.com/geo-mena/distillWrote 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/geo-mena/distill/cover)<a href="https://agentmods.dev/commands/geo-mena/distill/cover"><img src="https://agentmods.dev/badge/commands/geo-mena/distill/cover.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.00021 | $0.01384 |
| Opus 5 | $0.00010 | $0.00692 |
| Sonnet 5 | $0.00004 | $0.00277 |
| Haiku 4.5 | $0.00002 | $0.00138 |
Grade A, and why
cover 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 5d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load the distill-design skill, then produce a 1600×500 SVG cover banner for the project named in $@.
Workflow:
- Read
plugins/distill-design/SKILL.mddecision tree row "Cover banner for a project README" — it lists every measurement. Then read the canonical reference atplugins/distill-design/resources/covers/distill-design-system.svgand the article-hero source atplugins/distill-design/ui_kits/article/Chrome.tsx(ArticleHeadercomponent). - From $@, extract: project name (h1), one-sentence subtitle, and three byline cells (default labels: SCOPE, VALIDATED, OUTPUT — but adapt to the project; e.g. for a library it might be SURFACE, RUNTIME, SHIPS WITH). If the user only gave a name, ask one clarifying question for the subtitle and 3-cell content.
- Write a single self-contained SVG with
viewBox="0 0 1600 500", paper background#fdfdfd, and an embedded<style>block mirroringdistill-design-system.svgexactly — same class names, same sizes.
Layout (from the canonical reference; do not deviate):
- Background:
<rect width="1600" height="500" fill="#fdfdfd"/>. - Left column (eyebrow + h1 + subtitle + hairline + 3-col byline grid):
- Eyebrow: x=96 y=140, class
eyebrow—font-size: 12px; font-weight: 500; letter-spacing: 1.44px; fill: #6a6a6a;. Content: uppercase 2-token tagline ending in the project name's domain. - h1: x=96 y=200, class
h1—font-size: 56px; font-weight: 700; letter-spacing: -0.84px; fill: #000;. (Pure#000is allowed here — h1 is the only place.) - Subtitle: x=96 y=255, class
sub—font-size: 22px; font-style: italic; fill: #4a4a4a;. - Hairline rule:
<line x1="96" y1="296" x2="960" y2="296" stroke="#e8e8e4" stroke-width="1"/>. - 3-col byline grid: cells at x=96 / x=384 / x=672, label at y=320 (class
meta-label, 10px uppercase 0.1em fill#6a6a6a), value at y=346 (classmeta-value, 14px fill#2a2a2a), italic affiliation at y=367 (classmeta-aff, 13px italic fill#6a6a6a).
- Eyebrow: x=96 y=140, class
- Right column (FiLM-style fan-out diagram):
- Caption "prompt" (or context-appropriate noun) at x=1070 y=160, class
stack-label, text-anchor middle. - Input TensorVector: 4 stacked salmon cells, x=1056, widths 28, alternating shades from the
Primitives.tsxsalmon palette (#fdecea,#f8c2bb,#f5a39b,#fbd9d4), stroke#c44a3f. - Arrow input → block: solid
#6661.5px from (1098,240) to (1158,240), with a triangular#666arrowhead. - "Design system"-style block: 70×160 rounded rect at (1170,170), fill
#fbd9d4, stroke#c44a3f, with a vertical-rl label rotated -90° centered in the block (classvlabel, 13px medium fill#2a2a2a). - Fork stem: solid line (1240,240) → (1280,240).
- 3 orthogonal branches (90° bends, never diagonal): stem at x=1280 forks to top (y=175), mid (y=240), bottom (y=305), each ending at x=1322 with a triangular arrowhead.
- 3 output blocks at x=1334, width=120, height=40, rx=4, fill
#fdecea, stroke#c44a3f. Labels via classout-label(14px medium#2a2a2a), text-anchor middle, centered in each block. Use 3 nouns describing the project's output surface. - "n artifacts"-style mini-label below the bottom block, class
stack-label. - PointerGlyph end-stop: orange-yellow circle
#f5b942with white pointing-hand path (copy fromdistill-design-system.svg), translated to anchor the right edge near the mid output.
- Caption "prompt" (or context-appropriate noun) at x=1070 y=160, class
Hard constraints (non-negotiable):
- English only.
- No emoji.
- No year literals anywhere in the cover (
2017–2021is in the canonical reference because the canonical IS the system itself; for any other project, omit dates entirely or use timeless qualifiers). - No marketing superlatives in the subtitle. State what the project does in plain terms.
- Pure
#000is allowed on h1 only. Body labels stay#2a2a2a/#4a4a4a/#6a6a6a. - Strokes
#6661.5px rounded caps. No gradients, no shadows. - Output is a single self-contained SVG — embedded
<style>, no external font, no external<use href>.
Output location:
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.
- 5d ago First seen · 49 lines · 21 tokens per session scan A 237e4e9c37a6
cover is a command published in the GitHub repository geo-mena/distill (2 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 1,384 once invoked, about $0.0001 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-31.
Other commands, from other repositories
brand
Generate a full editorial brand-guidelines book for any URL. 14 chapters covering brand essence/archetype, colour, typography, spacing, shape, iconography, motion, components, voice, accessibility, tokens, and how-to-use guidance. Print-ready, dark-mode toggle, hand-off-ready single HTML.
pack
Bundle every designlang output (DTCG tokens, Tailwind, shadcn, Figma vars, motion, anatomy, Storybook, prompts) into one polished design-system directory ready to zip and ship.
verify
Fidelity check — rebuild a page from the extracted tokens, pixel-diff it against the live site, and score how faithfully the tokens capture the design.
battle
Head-to-head graded battle card between two sites — eight dimensions, bar-by-bar, verdict line.
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
figma-component-library
Generate a complete component library in Figma from a design system config — atoms, molecules, and organisms with all variants, auto layout, and component properties.