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 skills add IncommensurableHubris/fullstack-director --skill 02-designergit clone --depth 1 https://github.com/IncommensurableHubris/fullstack-directorWrote 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/incommensurablehubris/fullstack-director/02-designer)<a href="https://agentmods.dev/skills/incommensurablehubris/fullstack-director/02-designer"><img src="https://agentmods.dev/badge/skills/incommensurablehubris/fullstack-director/02-designer.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.00218 | $0.02892 |
| Opus 5 | $0.00109 | $0.01446 |
| Sonnet 5 | $0.00044 | $0.00578 |
| Haiku 4.5 | $0.00022 | $0.00289 |
Grade A, and why
02-designer 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
02 · Designer — realize (UX)
Sprint-scoped: invoked 02-designer sprint N. Realize the UX for sprint N's REQs — a tiered design system, a
spec per key screen, and a DM-ID manifest — all referencing the spine by REQ-NNN, never copying its prose.
You are the first skill to amend the spine: while realizing, you run the Reconcile step against
design-intent.md and emit structured amendment-log.json rows.
Operating principle — realize, and reconcile
Two moves, run together:
- Realize. Turn the thin
design-intent.mddeclaration + the sprint's REQs into a full design-system + screens (the realization). Reference REQs by ID; derive freely below the governed layer. - Reconcile (your debut of the amendment protocol). Challenge
design-intent.mdtwo ways: flesh-out — concretizederived/[NEEDS CLARIFICATION]intent (Tier-2 gate →stated); contradiction-flag — catch where the realization violates astatedintent, the a11y floor, or a Constitution non-negotiable (Tier-2 gate, or Tier-3 defer for scope). You run Reconcile inline — no subagent: design-intent conflicts are surfaced, obvious, and gated, so the fresh-context isolation that 03/05/07 need does not apply here.
The boundary-test = the token-governance line. Reconcile fires only on the governed layer (brand · semantic
tokens · the a11y floor · key screens · interaction principles · job-outcomes); the delegated layer (primitive
values · component tokens · layout/spacing · internals) is free realization — no amendment, ever. Full method:
references/reconcile-critique.md.
Profile switch — agent-system realizes the agent experience
Read the spine's Profile (the per-seat toggle table in shared/agentic-profile.md). Under webapp (default)
the flow below is unchanged. Under agent-system (or mcp-server), Phase B designs the agent experience, not
screens — the tool surface (names/descriptions are the interface; tool hit-rate is the quality metric), turns,
persona/voice, refusal-UX, and HITL touchpoints — per references/agent-experience.md. Phase A (tokens) and the
Reconcile machinery are unchanged; the DM-NNN manifest stays, but its rows point at tools/turns/refusals.
Reconcile's governed layer shifts to the design-intent voice + the agent-contract HITL rows; the WCAG floor
applies only where a GUI exists. Under skill-pack, 02 is skipped (trigger/description design folds into
03/04 + the skill-creator eval; status routes no design phase).
What ships with it
42 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/check_design.py 16 KB runs code
- evals/evals.json 7.1 KB
- evals/fixtures/aurora-clean/docs/planning/sprints/sprint-01.md 2.5 KB
- evals/fixtures/aurora-clean/docs/spec/amendment-log.json 23 B
- evals/fixtures/aurora-clean/docs/spec/architecture-constraints.md 653 B
- evals/fixtures/aurora-clean/docs/spec/capabilities/library.md 1.1 KB
- evals/fixtures/aurora-clean/docs/spec/capabilities/reader.md 767 B
- evals/fixtures/aurora-clean/docs/spec/design-intent.md 1.6 KB
- evals/fixtures/aurora-clean/docs/spec/specification.md 3.2 KB
- evals/fixtures/aurora-contrast/docs/planning/sprints/sprint-01.md 2.5 KB
- evals/fixtures/aurora-contrast/docs/spec/amendment-log.json 23 B
- evals/fixtures/aurora-contrast/docs/spec/architecture-constraints.md 653 B
- evals/fixtures/aurora-contrast/docs/spec/capabilities/library.md 1.1 KB
- evals/fixtures/aurora-contrast/docs/spec/capabilities/reader.md 767 B
- evals/fixtures/aurora-contrast/docs/spec/design-intent.md 1.7 KB
- evals/fixtures/aurora-contrast/docs/spec/specification.md 3.2 KB
- evals/fixtures/relay-agent/docs/planning/sprints/sprint-01.md 839 B
- evals/fixtures/relay-agent/docs/spec/agent-contract.md 1.9 KB
- evals/fixtures/relay-agent/docs/spec/amendment-log.json 23 B
- evals/fixtures/relay-agent/docs/spec/architecture-constraints.md 782 B
- evals/fixtures/relay-agent/docs/spec/capabilities/triage.md 1.9 KB
- evals/fixtures/relay-agent/docs/spec/design-intent.md 1002 B
- evals/fixtures/relay-agent/docs/spec/specification.md 1.3 KB
- evals/fixtures/teampulse/docs/discovery/assumption-map.md 1.8 KB
- evals/fixtures/teampulse/docs/discovery/charter.md 2.6 KB
- evals/fixtures/teampulse/docs/planning/backlog.md 6.2 KB
- evals/fixtures/teampulse/docs/planning/sprints/sprint-01.md 8.6 KB
- evals/fixtures/teampulse/docs/spec/amendment-log.json 23 B
- evals/fixtures/teampulse/docs/spec/architecture-constraints.md 1.6 KB
- evals/fixtures/teampulse/docs/spec/capabilities/digest.md 2.3 KB
- evals/fixtures/teampulse/docs/spec/capabilities/standups.md 2.4 KB
- evals/fixtures/teampulse/docs/spec/capabilities/team.md 2.6 KB
- evals/fixtures/teampulse/docs/spec/design-intent.md 1.7 KB
- evals/fixtures/teampulse/docs/spec/specification.md 5.7 KB
- evals/README.md 6.2 KB
- references/agent-experience.md 4.2 KB
- references/design-system.md 9.1 KB
- references/reconcile-critique.md 12 KB
- references/screen-spec.md 7.0 KB
- templates/design-system.md 7.8 KB
- templates/manifest.md 1.7 KB
- templates/screen.md 2.7 KB
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 · 131 lines · 218 tokens per session scan A 22c0ee1a8484
02-designer is a skill published in the GitHub repository IncommensurableHubris/fullstack-director (5 stars, last pushed 26d ago), licensed MIT. It adds 218 tokens to every session and 2,892 once invoked, about $0.0011 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
gsd-sketch
Sketch UI/design ideas with throwaway HTML mockups, or propose what to sketch next (frontier mode).
gsd-ui-phase
Generate UI design contract (UI-SPEC.md) for frontend phases.
gsd-ui-review
Retroactive 6-pillar visual audit of implemented frontend code.
userinterface-wiki
UI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.
larapilot-design
Produces isolated HTML/CSS mockups stored in .larapilot/mockups/ and served via a dev-only /mockups route. Use for "make a mockup", "dashboard concept", "landing page", or when planning needs visual references. Italian triggers include "mockup", "prototipo visivo".
ui-mockup
Generate HTML/CSS mockups for UI design. Produces browser-previewable mockup files with placeholder data. Use when the user says ui-mockup, mockup, design UI, wireframe, or needs visual reference for a feature.