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 skills/rchase999/aidd/aidd-corenpx skills add rchase999/aidd --skill aidd-coregit 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/skills/rchase999/aidd/aidd-core)<a href="https://agentmods.dev/skills/rchase999/aidd/aidd-core"><img src="https://agentmods.dev/badge/skills/rchase999/aidd/aidd-core.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.00058 | $0.01678 |
| Opus 5 | $0.00029 | $0.00839 |
| Sonnet 5 | $0.00012 | $0.00336 |
| Haiku 4.5 | $0.00006 | $0.00168 |
Grade A, and why
aidd-core 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIDD — the framework
Three phases. One gate. The gate is the point.
IDEATE RESEARCH [ GATE ] EXECUTE
sharpen -> sweep everything -> human chooses -> build
the idea findable in the browser under contract
Most AI development fails in the same place: the model quietly makes a hundred technical decisions the human never saw, and by the time anyone notices, the decisions are load-bearing. AIDD moves those decisions into one visible moment where a human can actually act on them — and then holds the build to what was decided.
Two modes
init auto-detects which one you are in and records it in state.json. aidd.mjs scan reports the evidence.
Greenfield — an empty or near-empty directory. Every decision is open.
Brownfield — a project already exists here. Most foundation decisions are closed, and re-asking them is worse than useless: it teaches the user to click through the gate without reading, which destroys the only thing the gate is for.
In brownfield mode:
aidd-surveyormaps the codebase first, into.aidd/00-context/codebase.md.- Closed decisions become
"locked": truesegments — rendered read-only on the gate, excluded from the submit requirement, delivered to the contract asLOCKED. They still get a note box, because "fine for now, but I want this gone next quarter" is real information. - The stack, its constraints, and the must-not-break list go in the top-level
contextblock ofoptions.json. Every stack entry needsevidence— the file that proves it — or validation fails. - Only genuinely open decisions get stances.
Locking is a judgement with teeth. Lock something that was actually open and you have made the user's decision for them behind their back. When it is borderline, leave it open with a strong recommendation and state what switching would cost.
Phase 1 — Ideate
Make the idea clear, not bigger. No technology, no feature lists, no roadmap.
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 · 124 lines · 58 tokens per session scan A ea46cd15eff8
aidd-core is a skill published in the GitHub repository rchase999/aidd (2 stars, last pushed 26d ago), licensed MIT. It adds 58 tokens to every session and 1,678 once invoked, about $0.0003 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 skills, from other repositories
audit-context
Evaluates ambient context artifacts (CLAUDE.md, memory, local skills, settings hooks) for compatibility with swarm governance. Returns a classified report so users can address interference before launching a team.
agentic-workflow-audit
Use when reviewing or auditing an existing agent / LLM-pipeline architecture — e.g. 'is my workflow actually decomposed or secretly a mega-agent?', 'are my task boundaries and success criteria right?' — even without the word 'audit'. ｜ 要檢視／review／稽核既有 agent 或 LLM pipeline 的架構，或問「有沒有拆好」「是不是變成 mega agent」「task…
writing-mode
Writing mode operational spec for the team lead. Returns lead identity, facilitator identity, ownership boundaries, editorial baseline, suggest-members guidance, and phase arc for writing-mode teams.
triage-mode
Triage mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for triage teams that diagnose an issue without changing it.
citation-receipts
Systematic per-citation verification protocol for academic writing. MUST be used whenever writing content that cites sources — papers, blog posts, SOTAs, or any document making factual claims about external work. Triggers (FR + EN) on any writing task involving references, citations, or bibliographic claims, or when…
sota-writer
Write structured State-of-the-Art (SOTA) reviews / literature reviews for academic research projects with zero hallucinated citations. Activate this skill whenever the user wants to write, update, or expand a SOTA. Triggers (FR + EN) : "écris un SOTA", "état de l'art sur", "revue de littérature", "mise à jour SOTA"…