Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rchase999/aidd/plugin install 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/research-dossier)<a href="https://agentmods.dev/skills/rchase999/aidd/research-dossier"><img src="https://agentmods.dev/badge/skills/rchase999/aidd/research-dossier.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.1 | $0.00045 | $0.01547 |
| Opus 5 | $0.00023 | $0.00773 |
| Sonnet 5 | $0.00009 | $0.00309 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
research-dossier 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 8d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The research sweep
The brief is in. Now find everything the project could be built from, and hand the user a real choice.
1. Derive the segments
A segment is one decision this project actually has to make, where a reasonable person could choose differently and the difference matters. Derive them from the brief. Do not paste a generic checklist — a static site generator and a hospital scheduler share almost no segments.
Draw from this catalogue as it applies:
Foundation — runtime and language · application framework · architecture shape (monolith / service / local-first / CLI) · package and build tooling
Data — storage engine · schema strategy · sync and offline model · external data sources and their licences · caching
Interface — UI framework or TUI · component and styling system · design language and typography · state management · accessibility floor
Intelligence (where relevant) — model provider · prompt vs fine-tune vs retrieval · eval strategy · cost ceiling
Delivery — hosting · CI · release cadence · migrations · observability
Constraints — auth model · licence compatibility · privacy and data residency · budget · the single hardest technical risk
Prior art — existing projects that already solve most of this, and whether to fork, port, wrap, or ignore them. Always search for this. Adopting a proven implementation usually beats writing a new one, and if you rejected that path the user deserves to see why.
Aim for 4–10 segments. Below 4 you probably folded real decisions into assumptions; above 10 the gate becomes a chore and people click through it.
On an existing codebase
Read .aidd/00-context/codebase.md first — dispatch aidd-surveyor if it is not there. Then sort every candidate segment:
- Closed — the codebase committed to it and changing it would be its own project. Emit as
"locked": truewith alockedReasonciting the file that proves it, and exactly one option: the thing actually in place. It still needs honest pros and cons; a locked segment is where you tell the user the truth about what they are living with. - Open — nothing in the code decides it. Research it as hard as you would greenfield.
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.
- 8d ago First seen · 128 lines · 45 tokens per session scan A e613bccabaf5
research-dossier is a skill published in the GitHub repository rchase999/aidd (2 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 1,547 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 skills, from other repositories
agentic-workflow-audit
A read-only review method for checking whether an AI-agent or language-model workflow is genuinely split into small, independent tasks with clear rules and checks.
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.
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"…
general-mode
General mode operational spec for the team lead. Returns lead identity, facilitator identity, suggest-members guidance, and phase arc for general-purpose teams. The silent fallback when outcomes fit no specific mode, and a wrapper base for custom workflows — it has no shortcut command.
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…