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-researcher)<a href="https://agentmods.dev/agents/0martinez/get-design-done/gdd-design-researcher"><img src="https://agentmods.dev/badge/agents/0martinez/get-design-done/gdd-design-researcher/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-researcher"><img src="https://agentmods.dev/badge/agents/0martinez/get-design-done/gdd-design-researcher.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.00040 | $0.00532 |
| Opus 5 | $0.00020 | $0.00266 |
| Sonnet 5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
gdd-design-researcher 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 11d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<research_areas>
UI Patterns
- How do similar products organize their primary navigation?
- What layout patterns are standard for this product type?
- How do similar products handle the key user flows?
- What data display patterns are common?
Competitor Analysis
- Visual language: color, typography, density, style
- What works well in competitor designs?
- What are common complaints about competitor UX?
- Where is there opportunity to differentiate?
Trends
- Current design trends relevant to this product category
- Which trends are likely timeless vs. temporary?
- Emerging patterns in the product's domain
Accessibility
- Accessibility patterns specific to the product domain
- Common accessibility failures in similar products </research_areas>
<execution_flow>
- Read BRIEF.md for context
- Research UI patterns for the product type
- Analyze 3-5 competitor/comparable products
- Identify current and timeless trends
- Write research files (patterns.md, competitors.md, trends.md)
- Synthesize into summary.md with actionable recommendations </execution_flow>
<output_format> Write to the research/ directory:
PATTERNS.md— UI patterns relevant to this productCOMPETITORS.md— Competitive analysisTRENDS.md— Trend analysisSUMMARY.md— Key findings and recommendations
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.
- 11d ago First seen · 67 lines · 40 tokens per session scan A 4d2de80e9789
gdd-design-researcher is an agent published in the GitHub repository 0martinez/get-design-done (5 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 532 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-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".
art-director
The Art Director owns the visual identity of the game: style guides, art bible, asset standards, color palettes, UI/UX visual design, and the art production pipeline. Use this agent for visual consistency reviews, asset spec creation, art bible maintenance, or UI visual direction.
Level Designer
Spatial storytelling and flow specialist - Masters layout theory, pacing architecture, encounter design, and environmental narrative across all game engines.
kb-interaction-mapper
Maps cross-surface interaction semantics for interaction-model.md from pre-filtered files.