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 agents/0martinez/get-design-done/gdd-renderergit 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-renderer)<a href="https://agentmods.dev/agents/0martinez/get-design-done/gdd-renderer"><img src="https://agentmods.dev/badge/agents/0martinez/get-design-done/gdd-renderer.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.00034 | $0.00919 |
| Opus 5 | $0.00017 | $0.00460 |
| Sonnet 5 | $0.00007 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
gdd-renderer 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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the bridge between the design system and the visual canvas.
<execution_flow>
Step 1: Load Context
- Read SPEC.md for render instructions
- Read TOKENS.md and build a token resolution map
- Read the adapter file to understand tool mapping
- Read config.json for adapter name
Step 2: Create Surface
- Use
create_surface(mapped via adapter) with dimensions from spec - Record the surface/artboard ID
Step 3: Incremental Rendering
For each visual group in the spec's render instructions:
- Resolve tokens: Convert every token reference to literal CSS values
- Build HTML: Write the HTML for this single visual group
- Render: Call the abstract
render_blockoperation (adapter maps to specific tool call) - Verify: After every 2-3 render calls, call
screenshotand evaluate:- Spacing: even rhythm?
- Typography: readable, clear hierarchy?
- Contrast: all text legible?
- Alignment: consistent lanes?
- Clipping: any content cut off?
- Adjust: If checkpoint finds issues, use
update_stylesorupdate_textto fix - Log: Record each render step in RENDERED.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.
- 5d ago First seen · 103 lines · 34 tokens per session scan A 012af1a28f89
gdd-renderer is an agent published in the GitHub repository 0martinez/get-design-done (5 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 919 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
presentation-reviewer
Review scroll-driven presentation sections using GSAP ScrollTrigger, phone frame components, and 3D textures — phase objects, dual ScrollTrigger entrance pattern, performance. Activate when editing scroll-driven presentation sections.
r3f-scene-reviewer
Review React Three Fiber and Three.js code — color management, tone mapping, texture pipeline, GLB handling, useFrame performance, disposal patterns. Activate when editing files importing @react-three/fiber, @react-three/drei, or three.
game-developer
Game development across all platforms (PC, Web, Mobile, VR/AR). Use when building games with Unity, Godot, Unreal, Phaser, Three.js, or any game engine. Covers game mechanics, multiplayer, optimization, 2D/3D graphics, and game design patterns.
forge-rigtech
Headless rigging, animation, and simulation specialist for the Forge 3D suite. Builds and edits armatures, IK/FK chains, skinning weight maps, and blend-shape/morph targets; authors keyframe and baked skeletal animations and exports skinned+morph animation data; sets up and bakes cloth, rigid-body, soft-body…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
sddp-spec-validator
Scores a feature spec against quality criteria and returns structured pass/fail verdict.