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/koroqe/claude-code-sdlc/design-foundationnpx skills add Koroqe/claude-code-sdlc --skill design-foundationgit clone --depth 1 https://github.com/Koroqe/claude-code-sdlcWrote 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/skills/koroqe/claude-code-sdlc/design-foundation)<a href="https://agentmods.dev/skills/koroqe/claude-code-sdlc/design-foundation"><img src="https://agentmods.dev/badge/skills/koroqe/claude-code-sdlc/design-foundation.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.1 | $0.00047 | $0.01143 |
| Opus 5 | $0.00023 | $0.00571 |
| Sonnet 5 | $0.00009 | $0.00229 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
design-foundation 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 6d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: Design Foundation
Generate .claude/rules/design.md — the project's design declaration. The harness ships the frame; this skill derives the project's own taste from its subject and writes it down, so every later UI slice extends one declared system instead of improvising a new one.
Arguments
$focus (also available as $ARGUMENTS) optionally names a surface, route, or area to prioritize during grounding. When absent, ground the whole product.
Invocation Context (determine FIRST)
Two paths reach this skill, and they differ in exactly one behavior:
- Standalone / interactive — the developer invoked
/design-foundationdirectly.AskUserQuestionis available for grounding gaps. - Unattended — triggered from
/bootstrap-feature— the pipeline reached this skill mid-run with nobody watching. Never callAskUserQuestionhere, and never stall waiting for an answer. Degrade to best-effort inference from the repository, and for anything that cannot be inferred write an explicitly labeled placeholder into the generated file — e.g.TODO(design-foundation): confirm the primary audience. An unattended run always completes.
If the invocation path cannot be positively determined, treat the run as unattended — ambiguity resolves to the path that cannot stall.
Process
1. Subject Grounding
Read the repository before asking anyone anything:
- the package/app manifest and README — what the product is and claims to do
- routes, page/screen files, navigation — the key surfaces
- user-facing copy — who the audience is and what register the product speaks in
From these, state: the concrete product, its audience, and, for each key surface, the single job that surface does. The subject's own world — its materials, instruments, vernacular — is where distinctive design choices come from; a generic template is where they go to die.
Ask via AskUserQuestion ONLY what cannot be inferred from the repository, and ONLY on the standalone path (see Invocation Context). Never ask a question the repository already answers.
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.
- 6d ago First seen · 68 lines · 47 tokens per session scan A 6551ec960ced
design-foundation is a skill published in the GitHub repository Koroqe/claude-code-sdlc (51 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 1,143 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 skills, from other repositories
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…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
waitlist-page
【模板: 等候名单页 / Waitlist】 【意图】为新产品 / 早鸟内测做一张极简等候页。 【布局】.
design-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to design, redesign, critique, audit, polish, harden, optimize, adapt, clarify, colorize, animate, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, onboarding, empty states…