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 skills/codejunkie99/agentic-stack/design-mdnpx skills add codejunkie99/agentic-stack --skill design-mdgit clone --depth 1 https://github.com/codejunkie99/agentic-stackWhat 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.00002 | $0.00879 |
| Opus 5 | $0.00001 | $0.00439 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
design-md 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 yesterday.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DESIGN.md — portable visual system contract
Use this skill when a task touches Google Stitch's DESIGN.md format or
the project explicitly references its design system / design tokens. The
skill loads only when DESIGN.md exists at the project root (see
preconditions above), so general UI / frontend / component work that
isn't tied to a DESIGN.md won't trip it.
Source of truth
DESIGN.mdis a contract file. Read it before changing visual UI.- Treat YAML front matter tokens as normative values: colors, typography, spacing, radius, and component tokens are exact inputs to code.
- Treat the Markdown body as design rationale: it explains mood, hierarchy, interaction intent, and where tokens should or should not be used.
- If no
DESIGN.mdexists this skill is inactive; for new UI, offer to create one or ask for a brand/reference, but don't generate one unprompted.
Default: read-only
Do not modify DESIGN.md unless the user explicitly asks for a design
system change. Implementation work consumes the contract; it does not
edit it. Token additions, renames, or section restructures land in their
own commit with a clear message and (ideally) a Stitch round-trip.
Implementation rules
- Map tokens into the local styling system already in use: CSS variables, Tailwind theme values, design-token JSON, component props, or native styles.
- Use token references and component patterns from
DESIGN.mdinstead of hard-coded one-off values. - Keep accessibility constraints intact. Do not weaken contrast, focus, reduced-motion, or touch-target guidance unless the user explicitly asks.
When an edit IS authorised
- Preserve unknown headings and extra prose; other agents or Stitch may own them.
- Express component variants as related entries
(
button-primary,button-primary-hover, etc.). - Land token / structure changes in their own commit, separate from the feature consuming them.
Validation
- If Node/npm tooling is available, lint with:
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.
- yesterday First seen · 93 lines · 2 tokens per session scan A 266183028885
design-md is a skill published in the GitHub repository codejunkie99/agentic-stack (2,241 stars, last pushed 25d ago), licensed Apache-2.0. It adds 2 tokens to every session and 879 once invoked, about $0.0000 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…