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/design-guardnpx skills add Tradebaas/Groundwork --skill design-guardgit clone --depth 1 https://github.com/Tradebaas/GroundworkWrote 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/tradebaas/groundwork/design-guard)<a href="https://agentmods.dev/skills/tradebaas/groundwork/design-guard"><img src="https://agentmods.dev/badge/skills/tradebaas/groundwork/design-guard.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.00087 | $0.01461 |
| Opus 5 | $0.00044 | $0.00731 |
| Sonnet 5 | $0.00017 | $0.00292 |
| Haiku 4.5 | $0.00009 | $0.00146 |
Grade A, and why
design-guard 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 4d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design-guard: look at it before you ship it
Render the thing (screenshot, preview, generated document, a real run of the command) and check that, not the source. DESIGN.md and VOICE.md are the measuring stick; this catches what automation cannot.
Impeccable, the installed design method, owns the making of a frontend: its craft floor, its detector and its finish reviewer are the rulebook for one, and this skill does not carry a second copy of it. Route first, then check.
| What you are about to deliver | Who judges it |
|---|---|
| A web, iOS, Android or adaptive interface | The method built it. Section 2: re-check, never re-hunt |
| A generated document, e-mail, export, error message, CLI or log output, notification | This skill. Section 3 |
| An interface on a platform the method does not carry: Unity, Godot and other game engines, console UIs, embedded and kiosk displays, TV, print | This skill. Section 3, and the verdict says no design method covered it |
1. The floors, on every route
Neither of these is negotiable by a direction, a template, or a medium, and neither is stated in the method's own guidance, so they are checked here whatever route you took.
- Accessibility floor: contrast, focus order, labels on inputs and icons, keyboard path through the flow. (Legal baseline: see COMPLIANCE.md.) On a document: reading order and tagged structure. In any medium: never color alone carrying the meaning.
- Reduced motion (DESIGN.md principle 7): anything that moves collapses to static under the
user's
prefers-reduced-motion: reduce, with the content still readable. Exercise the preference, do not read the CSS for it.
2. A frontend: re-check against what was committed
The craft floor already ran, the detector already ran, and a reviewer that never saw the build thread already scored the result. Start from those, and report what is still open.
- The direction contract was kept. It is the opening comment in the artifact (THESIS, OWN-WORLD, STORY, FIRST VIEWPORT, FORM). Read it beside the render: a block describing something the page does not do is the finding. A contract the production build erased is its own finding, because nothing can be audited against it.
- The FINISH line is discharged. The contract closes with the run's exit condition. A page that looks complete with the finish review never run is abandoned, not done.
- The finish verdict travels as it stands. Its open items stay open until they are fixed, under the reviewer's own disposition word. Never summarized into a pass.
- The live-surface contract, on a redesign (
designstep 3): URLs and slugs, page titles and structured data, navigation labels, form field names and their order, analytics names, the wordmark, legal and consent copy. Anything on that list that moved without the owner saying so is a finding, and what does move ships with redirects. - DESIGN.md section 3 still mirrors the built world. It is written from the build after the finish review; code is the source of truth, so tokens that moved since leave a stale mirror.
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.
- 4d ago First seen · 95 lines · 0 tokens per session scan A d63be503162f
design-guard is a skill published in the GitHub repository Tradebaas/Groundwork (2 stars, last pushed 9d ago), licensed MIT. It adds 87 tokens to every session and 1,461 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
mission-driver
Create roadmaps and mission configs, then drive the mission-driver AI dev-loop engine. mission-driver lives at tools/mission-driver/ — it reads missions/ .json and loops CHECK → REVIEWPLANS → EXECPLANS → DRAFTPLANS → DEEPAUDIT until the roadmap is done or the audit budget is exhausted. Use this skill when the user…
keel-plan
Create or revise PLAN.md — propose the phase DAG (phases · gates · dependencies) from the user's goal, get approval, write the table and regenerate the colored Mermaid diagram from it. Statuses flip at rituals (/keel-handover, /keel-phase-review); post-completion fixes land in the Fix log.
keel-stats
Render the ritual telemetry visually — turns .claude/ritual-log into reports/ritual-stats.md with PLAN.md-style colored Mermaid interval boxes (session/compact boundaries) + a counts table. Answers "which skills/commands/hooks ran, how often, in which interval".
sdd-serve
Serve the SDD Builder's AI request queue: claim requests with sddnextrequest, draft the proposal, answer with sddrespondrequest. Never writes spec files — the user accepts each proposal in the builder. Use when the user asks to attend, serve or listen to the SDD board queue. / Atiende la cola de peticiones del SDD…
init
Configure an uninitialized project from an approved charter: stack, scripts, identity, optional Git, and verification.
sdd-workflow
Guide a project with Spec-Driven Development (SDD) discipline - idea, approved spec, consistent plan, tasks, a gate that verifies approval and consent, implementation, validation, and logbook. Bilingual EN/ES. Use when the user wants to start, spec, plan, implement, or validate work with SDD, or mentions specs, plans…