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/cloud-archgit 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/cloud-arch)<a href="https://agentmods.dev/commands/geo-mena/distill/cloud-arch"><img src="https://agentmods.dev/badge/commands/geo-mena/distill/cloud-arch.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.00016 | $0.01076 |
| Opus 5 | $0.00008 | $0.00538 |
| Sonnet 5 | $0.00003 | $0.00215 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
cloud-arch 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 3d 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 — 44 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 cloud architecture SVG for the system described in $@.
Workflow:
- Read
plugins/distill-design/SKILL.mddecision tree row "Cloud architecture diagram" andplugins/distill-design/DESIGN-SYSTEM.md§ "Service icons for architecture diagrams" before drawing. The category→color mapping and the missing-icon protocol live there. - Identify every service in the brief. For each, find the matching
<symbol id="service-<slug>">inplugins/distill-design/resources/diagrams/_service-icons.svg. The library has 29 vendor-agnostic icons across EDGE & DNS, NETWORKING, COMPUTE, STORAGE, DATA, IDENTITY, MESSAGING, OBSERVABILITY, EXTERNAL SINKS. If a service is missing, either map it to the closest existing icon (e.g. AWS Lambda →service-function, GCP Pub/Sub →service-pubsub, BigQuery →service-databasefor now) or follow the missing-icon protocol in DESIGN-SYSTEM.md to draw a new 24×24 thin-stroke symbol and add it to the library before consuming it. - Inline-copy every needed
<symbol>block byte-for-byte from_service-icons.svginto the consumer SVG's own<defs>. Reference each symbol via<use href="#service-<slug>" width="20" height="20"/>inside its enclosing block. Do not use cross-file<use href="../_service-icons.svg#...">— GitHub<img src>andfile://both block it. - Lay out the architecture in horizontal bands or boxed regions: EDGE → NETWORKING → COMPUTE → DATA → OBSERVABILITY, with region/VPC/account boundaries as paper-fill
#fdfdfdrectangles with a#d8d8d41px hairline and a 12px uppercase#6a6a6aletter-spacing 0.1em label in the corner. - Use
plugins/distill-design/resources/diagrams/multi-region-observability.svgas the canonical layout reference;cloudflare-tunnel-routing.svgandmulti-tier-rds.svgas secondary references.
Color rules (from DESIGN-SYSTEM.md § "Service icons for architecture diagrams"):
- Color goes on the enclosing block, never on the icon stroke. Icon stroke stays
#666regardless. - Edge / CDN / compute / orchestration (DNS, CDN, load balancer, autoscaler, compute, function, container, kubernetes, api-gateway) → block fill
#d6e4f3, block stroke#356aa8. - Data / endpoints (database, nosql, object-storage, block-storage, cache, pub/sub, queue, email, slack) → block fill
#fdeceaor#fbd9d4, block stroke#c44a3f. - Observability (metrics, logs, alarms, events, dashboard) → block fill
#ddd9ee, block stroke#b8a8d8. - Region / VPC / account boundary → paper fill
#fdfdfd, hairline#d8d8d4, label as above.
Arrow rules:
- Solid
#6661.5px arrow for primary data flow. - Dashed
stroke-dasharray="3 3"for failover, observability bus, monitoring scrape, async fanout. Label dashed arrows in 10px italic#6a6a6anext to the line.
Output location:
- Always:
plugins/distill-design/resources/diagrams/<slug>.svg. Slug from the architecture purpose, not the vendor (e.g.multi-az-web-app.svg, notaws-web-app.svg). - Include a
<title>and<desc>element at the top of the SVG narrating the bands and flow, mirroringmulti-region-observability.svg.
Hard constraints (non-negotiable):
- English only.
- Never import vendor-official AWS / GCP / Azure / Cloudflare icons. They violate the no-multi-color, no-fill, low-saturation rules. Always use the bespoke
service-<slug>library. - No emoji. No multi-color icons. No gradients, no shadows. Stroke
#6661.5px rounded caps for icons; block strokes per the category color above. - No year literals anywhere in the SVG (
<title>,<desc>, labels). - Body / label color
#2a2a2aor#6a6a6a; never pure#000.
Verification:
- Open the SVG with
chrome-devtoolsand screenshot. The user has caught icon misalignment and stroke-color drift visually before. Runchrome-devtools list_console_messagesto surface any<use>resolution warnings. - If a new symbol was added to
_service-icons.svg, also re-screenshot any existing diagram that uses adjacent symbols to confirm no regression.
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.
- 3d ago First seen · 44 lines · 16 tokens per session scan A a679899f1091
cloud-arch is a command published in the GitHub repository geo-mena/distill (2 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,076 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.
pair
Fuse two extracted designs into a single hybrid identity. Pick which axis (colour, typography, spacing, shape, motion, voice, components) comes from which site. Defaults to "visual A × voice B" — same colours/spacing as the first URL, type/voice/components from the second.
theme-swap
Recolour an extracted site's design around a new brand primary. OKLCH hue rotation preserves perceptual lightness — neutrals, type, spacing, and motion stay untouched. Side-by-side HTML preview + recoloured tokens (DTCG, Tailwind, shadcn, Figma).
dna
Place a design in the measured design space — nearest systems, per-axis percentiles, outliers.
extract
Extract the complete design language from a URL — DTCG tokens, Tailwind, Figma vars, motion, voice, components.
fidelity
Measure how faithfully a clone reproduces a site — pixel-diff plus motion-fidelity into one 0-100 score, a letter grade, a ranked correction plan, and a shareable card.