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 commands/rchase999/aidd/gategit clone --depth 1 https://github.com/rchase999/aiddWhat 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.00015 | $0.00693 |
| Opus 5 | $0.00008 | $0.00347 |
| Sonnet 5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
gate 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 2d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Research Gate
Load the decision-gate skill for the page contract and theming rules.
Arguments: $ARGUMENTS
If --ingest <file> was passed
The user submitted from a page opened without the server. Skip straight to:
node "${CLAUDE_PLUGIN_ROOT}/scripts/aidd.mjs" ingest "<file>"
Then continue at After the gate passes below.
Otherwise
1. Check the inputs
node "${CLAUDE_PLUGIN_ROOT}/scripts/aidd.mjs" validate
If options.json is missing or invalid, stop — the gate cannot be honest about research that isn't there. Go back to /aidd:research.
2. Build the page
node "${CLAUDE_PLUGIN_ROOT}/scripts/aidd.mjs" scaffold-gate
That drops the working template at .aidd/02-research/gate.html.
Now theme it for this project — dispatch the aidd-gate-designer agent, giving it the project brief and options.json. Everything above the THEME LAYER ENDS marker in the stylesheet is its to rewrite, as is the hero markup and the theme block in options.json. The mechanism below that marker is not.
The contract you must not break:
- the page reads
window.AIDD_OPTIONS(the server injects it — never inline your own copy) - the page calls
window.AIDD.submit(payload)with the documented payload shape <!-- AIDD:INJECT -->stays in<head>- every option keeps three stance buttons, its pros, its cons, and its source links
3. Serve it and wait
Run in the background — the process exits the moment the user submits, which is how you find out:
node "${CLAUDE_PLUGIN_ROOT}/scripts/gate-server.mjs" --timeout 90
Tell the user the browser is opening and that nothing is sent back until they press Submit decisions. Then stop and wait. Do not write product code, do not "get a head start on scaffolding", do not guess which options they will pick. The gate is a gate.
Exit codes: 0 submitted · 2 timed out or interrupted · 3 bad inputs.
If it times out, say so plainly and offer to re-serve. A timed-out gate is not a passed gate.
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.
- 2d ago First seen · 70 lines · 15 tokens per session scan A 9a4fb2a9d258
gate is a command published in the GitHub repository rchase999/aidd (2 stars, last pushed 23d ago), licensed MIT. It adds 15 tokens to every session and 693 once invoked, about $0.0001 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 commands, from other repositories
dial
Live value calibration - 2-4 lettered candidates injected into the running app; click through them against real data, nothing written to source.
adapt-framework
Adapt KATA and repository tooling after an approved no-write analysis and plan.
break-down-tests
Explain existing automated tests and assertions without editing code.
fix-traceability
Audit and repair one ticket's TMS traceability after explicit approval.
jira-components
Plan and reconcile Jira Components after explicit approval.
jira-instance-migration
Repoint Jira configuration and regenerate catalogs after explicit approval.