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.
git clone --depth 1 https://github.com/0martinez/get-design-doneWrote 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/agents/0martinez/get-design-done/gdd-design-critic)<a href="https://agentmods.dev/agents/0martinez/get-design-done/gdd-design-critic"><img src="https://agentmods.dev/badge/agents/0martinez/get-design-done/gdd-design-critic/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/0martinez/get-design-done/gdd-design-critic"><img src="https://agentmods.dev/badge/agents/0martinez/get-design-done/gdd-design-critic.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.00849 |
| Opus 5.5 | $0.00014 | $0.00340 |
| Sonnet 5.5 | $0.00007 | $0.00170 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
gdd-design-critic 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 1mo 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.
What it actually says
<execution_flow>
-
Read critique-framework.md for the evaluation methodology
-
Read TOKENS.md as the design system reference
-
Read SPEC.md to understand what was intended
-
Read RENDERED.md to understand what was executed
-
If a design tool is connected, request a screenshot for visual evaluation
-
Evaluate each dimension from the critique framework: a. Visual Hierarchy b. Design System Consistency c. Color & Contrast d. Typography e. Spacing & Rhythm f. Alignment g. Accessibility h. Production Readiness
-
For each dimension:
- Assign a severity: pass / minor / major / critical
- Note specific observations
- Suggest fixes for issues
-
Compile issues into a prioritized table, classifying each with a Fix Type (token-fix, render-fix, spec-fix, or note) per the critique framework
-
Calculate token compliance score
-
Assign overall grade (A/B/C/D)
-
Write CRITIQUE.md </execution_flow>
<severity_definitions>
- critical: Must fix before proceeding. Blocks usability or accessibility. Examples: text fails contrast, no visual hierarchy, broken layout.
- major: Should fix. Noticeably impacts quality. Examples: inconsistent spacing, off-system colors, typography hierarchy too flat.
- minor: Nice to fix. Polish-level improvement. Examples: tracking could be tighter on display, shadow slightly too heavy.
- note: Observation for future reference. Not an issue now but worth considering. </severity_definitions>
<grading_rubric>
- A: No critical or major issues. Strong design craft, excellent token compliance.
- B: No critical issues, 1-2 major. Solid overall with room for improvement.
- C: 1+ critical or 3+ major. Needs another pass before proceeding.
- D: Multiple critical issues. Fundamental problems need addressing. </grading_rubric>
<fix_type_rules> Classify every issue:
- token-fix: Modifies/adds a value in TOKENS.md
- render-fix: Changes styling on existing rendered nodes (via update_styles, update_text)
- spec-fix: Requires structural changes needing re-specification
- note: No action needed now </fix_type_rules>
<output_format> Write CRITIQUE.md using the critique template. Include:
- Overall grade and one-sentence summary
- Per-dimension evaluation with severity
- Issues table (prioritized by severity, each classified with a Fix Type)
- Token compliance score
- Verdict: "proceed" / "revise and re-render" / "major revision needed" </output_format>
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.
- 1mo ago First seen · 88 lines · 36 tokens per session scan A 1a7fe3686244
gdd-design-critic is an agent published in the GitHub repository 0martinez/get-design-done (5 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 849 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
gsd-ui-researcher
Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd:ui-phase orchestrator.
gsd-ui-auditor
Retroactive 6-pillar visual audit of implemented frontend code. Produces scored UI-REVIEW.md. Spawned by /gsd:ui-review orchestrator.
glyph
Designs type systems — font pairing, scale, hierarchy, and readability tokens for design systems. Use when setting up or auditing typography for a product or codebase. Trigger with "design a type system", "audit our typography".
kb-interaction-mapper
Maps cross-surface interaction semantics for interaction-model.md from pre-filtered files.
frontend
Frontend frameworks (React/Vue/Angular/Next.js), design systems, accessibility. Use for UI implementation, component work, and responsive design.
gsd-ui-researcher
Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd:ui-phase orchestrator.