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/aaronbassett/agent-foundry/implementnpx skills add aaronbassett/agent-foundry --skill implementgit clone --depth 1 https://github.com/aaronbassett/agent-foundryWhat 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.00072 | $0.01607 |
| Opus 5 | $0.00036 | $0.00804 |
| Sonnet 5 | $0.00014 | $0.00321 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade A, and why
design-systems:implement 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 2d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Design System
Read DESIGN.md and apply its tokens to the project's existing style files.
DESIGN.md Discovery
Find DESIGN.md using this search order:
- Check CLAUDE.md in cwd for a reference to DESIGN.md
- Look for DESIGN.md in cwd
- Search upward from cwd
- Search common locations: project root,
src/,packages/*/ - If not found, tell the user: "No DESIGN.md found. Run
/design-systems:createfirst."
Use Glob to search: **/DESIGN.md
Implementation Flow
Step 1: Parse the Design System
Extract all implementable tokens from DESIGN.md:
- Colors: Every hex value with its token name from the Palette subsection
- Typography: Font families, sizes (rem), weights, line-heights from the Type Scale table
- Spacing: Base unit and all derived values from the Spacing Scale table
- Shadows: Exact CSS values from Shadow Definitions
- Radius: Border-radius values from the Components section
- Any other CSS-expressible values mentioned in the schema
Step 2: Detect Framework/CSS Setup
Scan the project for the styling approach:
| Indicator | Framework | Token Format |
|---|---|---|
tailwind.config.* present |
Tailwind CSS | Extend theme in config file |
*.module.css or *.module.scss files |
CSS Modules | CSS custom properties in global stylesheet |
styled-components or @emotion in package.json |
CSS-in-JS | Theme object exported from a theme file |
*.css or *.scss files present |
Vanilla CSS/SCSS | CSS custom properties in a variables file |
*.vue files with <style> blocks |
Vue SFC | CSS custom properties in global stylesheet |
*.svelte files with <style> blocks |
Svelte | CSS custom properties in global stylesheet |
| None detected | Unknown | Ask user; default to CSS custom properties |
Use Glob to detect: **/tailwind.config.*, **/*.module.css,
**/*.module.scss, **/*.vue, **/*.svelte.
Use Grep to check package.json for styled-components or @emotion.
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.
- 2d ago First seen · 209 lines · 72 tokens per session scan A 41627927b6d9
design-systems:implement is a skill published in the GitHub repository aaronbassett/agent-foundry (4 stars, last pushed 17d ago), licensed MIT. It adds 72 tokens to every session and 1,607 once invoked, about $0.0004 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 skills, from other repositories
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
author-component
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…