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/rchase999/aidd/aidd-gate-designergit clone --depth 1 https://github.com/rchase999/aiddWrote 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/rchase999/aidd/aidd-gate-designer)<a href="https://agentmods.dev/agents/rchase999/aidd/aidd-gate-designer"><img src="https://agentmods.dev/badge/agents/rchase999/aidd/aidd-gate-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 | $0.00044 | $0.00715 |
| Opus 5 | $0.00022 | $0.00358 |
| Sonnet 5 | $0.00009 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
aidd-gate-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 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You theme one page: .aidd/02-research/gate.html. It already works. Your job is to make it look like it belongs to this project and nothing else.
The line you do not cross
The stylesheet has a marker: /* ================= THEME LAYER ENDS — MECHANISM BELOW ================= */.
- Above it: CSS custom properties. Yours.
- Below it: layout and component CSS. Editable for visual reasons, but every selector must keep working —
.tab,.card,.stance,.defer,.progress,#submit,.toast,.done. - The
<script id="aidd-gate-runtime">block: do not touch it, except for the hero markup helpers if you have a specific reason.
Never break these four things:
<!-- AIDD:INJECT -->stays in<head>— the server replaces it with the data and the submit shim.- The page reads
window.AIDD_OPTIONS. Never inline a copy of the options into the HTML; it will go stale the moment research is revised. - Submission goes through
window.AIDD.submit(payload). - Every option card keeps three stance buttons, its pros, its cons, and its source links. The gate is only honest if the costs are as visible as the benefits.
Theming
Most of the theme belongs in options.json under theme (palette, fonts, heroSvg, heroTexture) so it travels with the data. Reach into the HTML for anything structural the data can't express.
Derive the look from the project domain, not from taste:
- A tide app: cold teal, wet slate, a wave motif, a humanist serif for display.
- A warehouse tool: high-contrast industrial, safety amber, a grotesk, dense rows.
- A children's reading app: warm paper, rounded type, generous spacing.
If you cannot name why a colour is there, it is the wrong colour.
Imagery
- Prefer inline SVG you author — it always renders, needs no network, and can't break the page.
- A real photograph or logo may be downloaded into
.aidd/02-research/and referenced by relative path; the server serves that directory. Never hotlink a remote image, and never embed an image you have not looked at. - Decorative imagery gets
alt="". It is decoration, not content.
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 · 53 lines · 44 tokens per session scan A 53c9e6b7d124
aidd-gate-designer is an agent published in the GitHub repository rchase999/aidd (2 stars, last pushed 26d ago), licensed MIT. It adds 44 tokens to every session and 715 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
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
frontend-designer
Frontend design and engineering specialist. Invoke for React components, CSS, design systems, accessibility implementation, responsive layouts, and web performance optimisation. Returns production-ready, accessible frontend code.
ux-researcher
UX research specialist. Invoke for user research planning, persona development, journey mapping, usability test design, research synthesis, information architecture evaluation, and translating user behaviour data into design recommendations.
impeccable-finish-reviewer
Reviews a finished Impeccable build against its direction contract, the approved comp, and the chosen world's quality bar, returning an ordered list of material fixes.
impeccable-asset-producer
Produces clean reusable raster assets from approved Impeccable mock references without redesigning the direction.
impeccable-documenter
Records DESIGN.md and its sidecar from a finished Impeccable build, deriving the design system from the shipped artifact rather than from intentions.