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/tradebaas/groundwork/designnpx skills add Tradebaas/Groundwork --skill designgit clone --depth 1 https://github.com/Tradebaas/GroundworkWhat 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.00106 | $0.02451 |
| Opus 5 | $0.00053 | $0.01226 |
| Sonnet 5 | $0.00021 | $0.00490 |
| Haiku 4.5 | $0.00011 | $0.00245 |
Grade A, and why
design 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design: nothing ships looking or sounding like a default
Groundwork does not make interfaces itself. Making one runs on impeccable, the design method
begin installs per project (node checks/design-method.mjs --install; the enforcement line at
the top of node checks/check.mjs says whether this project has it, and which release). This skill
is the Groundwork side of that seam. It carries what is genuinely ours, hands it over as binding
input, and holds open the three points where the owner decides.
docs/DESIGN.md sections 1 and 2 and docs/design/VOICE.md carry the durable principles and the
owner's standing defaults. DESIGN.md section 3 is not written here: it is recorded from the
world that was actually built, after the finish review (step 4). A rulebook written before the
build gets defended against reality instead of describing it.
Where the two documents live. The method reads docs/DESIGN.md and writes its product record
to docs/PRODUCT.md, because docs/ is one of the directories it searches by itself. Neither
path is configured anywhere, and neither moves. The product record holds what
docs/product/BRIEF.md does not own (platform, stack, brand commitments, evidence on hand,
accessibility needs) and points at the brief for scope, users and purpose: a fact that stands in
both files is a fact that will disagree with itself later.
No design method installed (a project that started without an interface, a failed install recorded in STATE.md)? Install it first. Everything below assumes it is there.
1. Ask the owner: only what is theirs
Two questions, and only these: the method asks the rest at the point where the answer changes the work, and asking twice is how an owner learns their answers do not travel.
- Brand reality: existing logo, colors, fonts, brand guide? If yes, that is binding: collect
the files into
docs/design/reference/and carry them over as a brand commitment in step 3. If no, nothing is blocked; the direction round derives a brand with the owner. - Voice: product language (NL/EN/...), register (je/u/you), and whether this audience changes the standing voice default in VOICE.md.
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 · 152 lines · 0 tokens per session scan A e83274d540d5
design is a skill published in the GitHub repository Tradebaas/Groundwork (2 stars, last pushed 7d ago), licensed MIT. It adds 106 tokens to every session and 2,451 once invoked, about $0.0005 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
review-creative
Audit customer-facing work for UX, accessibility, brand fit, credibility, and generic AI output. Use for design, marketing, document, presentation, or visual review.
design-experience
Build distinctive production-grade app and web interfaces. Use for UI/UX, responsive states, accessibility, visual systems, redesigns, or frontend polish.
design-interaction
Design the interaction + feedback + error flows for a user-facing surface (CLI, API, or web). On-demand — run when the ux-engineer is consulted on an interaction contract.
design-visual-asset
Produce a project visual asset — social card, README banner, logo/avatar, or favicon — as self-contained, accessible SVG. On-demand.
product-design
把任何产品（Web / App / CLI / 库 / 更抽象的产品）从模糊想法收敛成「一个问题→一个输出→一个决定」的契约。当用户要定义新产品、设计功能、画界面、纠结要不要加某个功能、或说产品变臃肿了要瘦身时使用。.
ai-concept-generation
Use when preparing landscape AI concept prompts, generating multiple visual directions from a measured base plan, logging generation batches, selecting variants, and protecting geometry from AI drift.