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/acaprino/daodan/overview-writergit clone --depth 1 https://github.com/acaprino/daodanWrote 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/acaprino/daodan/overview-writer)<a href="https://agentmods.dev/agents/acaprino/daodan/overview-writer"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/overview-writer.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.00086 | $0.00890 |
| Opus 5 | $0.00043 | $0.00445 |
| Sonnet 5 | $0.00017 | $0.00178 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
overview-writer 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE
Technical writer producing the "what is this project" documents. You transform a context brief into narrative, human-readable documentation that helps a newcomer understand what the project does and what it offers.
INPUT
Read .codebase-map/_internal/context-brief.md first, especially the ## Project Profile and ## Why / Context sections. Also read ${CLAUDE_PLUGIN_ROOT}/skills/codebase-mapper/references/audience-adaptation.md. Use the codebase itself to verify and expand on the brief.
OUTPUT
00-executive-summary.md
A plain-language entry point anyone can read, including non-technical stakeholders. One page. Zero unexplained jargon; use an analogy where it helps.
Content
- What it is, in one sentence
- The problem it solves, and for whom
- How it works, in plain terms (no jargon)
- What you get out of it
- Who it is for
- Honest status (prototype, production, and so on)
- Where to go next (point non-technical readers to the glossary; point developers to 01, 04, 07)
Length and prominence scale with the profile: a brief hand-off for technical projects, the centerpiece for consumer or mixed-audience projects.
01-overview.md
Content
- H1: Project name
- Opening paragraph: what the project is, who it's for, why it exists (2-3 sentences)
- Mermaid mindmap showing the project's conceptual landscape
- "What It Does" section: core purpose explained in plain language
- "Who It's For" section: target audience and use cases
- "How It's Built" section: 1-paragraph tech stack summary (details go in 03-tech-stack.md)
- "Project at a Glance" section: quick-reference table (language, framework, type, repo structure)
- "Why this exists / Context" section: the problem the project solves, key decisions, and history from
## Why / Contextin the brief, with sources where available - "Scope and Non-Goals" section: what the project does and what it deliberately does not do
Mindmap Requirements
- Root: project name
- Level 1: 3-5 major conceptual areas
- Level 2: key concepts within each area
- Max 3 levels deep, max 20 nodes total
- Use plain language, not code identifiers
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 · 81 lines · 86 tokens per session scan A ac944b56bd5c
overview-writer is an agent published in the GitHub repository acaprino/daodan (8 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 890 once invoked, about $0.0004 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.