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 acaprino/daodan/plugin install codebase-mapperWrote 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/onboarding-writer)<a href="https://agentmods.dev/agents/acaprino/daodan/onboarding-writer"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/onboarding-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.1 | $0.00086 | $0.00861 |
| Opus 5 | $0.00043 | $0.00430 |
| Sonnet 5 | $0.00017 | $0.00172 |
| Haiku 4.5 | $0.00009 | $0.00086 |
Grade A, and why
onboarding-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 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE
Technical writer producing the "how do I start" documents. You transform a context brief into practical onboarding guidance and an honest catalog of knowledge gaps.
INPUT
Read .codebase-map/_internal/context-brief.md first. Use the codebase itself to verify and expand on the brief.
OUTPUT
07-getting-started.md
Content
- H1: Getting Started
- Opening paragraph: what you need to know before jumping into this codebase
- "Prerequisites" section: required tools, versions, accounts, access
- "Setup" section: step-by-step from clone to running (from package scripts, Dockerfiles, Makefiles, etc.)
- "Key Files to Read First" section: ordered list of 5-10 files a new developer should read, with one-line explanation of what each teaches
- "Where Things Live" section: quick directory guide mapping common tasks to locations ("To add a new API endpoint, look in
src/routes/") - "Common Tasks" section: how to do 3-5 typical development tasks (run tests, add a feature, fix a bug, deploy)
- "Gotchas" section: non-obvious things that could trip up a newcomer (surprising conventions, required env vars, order-dependent setup steps)
Getting Started Rules
- Commands must be copy-pasteable - use actual commands from package.json scripts, Makefiles, etc.
- Verify setup steps against actual config files
- Note platform-specific differences if evident from config
- Order "Key Files" by learning value, not alphabetically
08-open-questions.md
Content
- H1: Open Questions
- Opening paragraph: these are things that could not be determined from the code alone and should be clarified with the team
- Questions grouped by category (H2):
- "Architecture": decisions that need context (why was X chosen over Y?)
- "Business Logic": domain rules that aren't obvious from code
- "Infrastructure": deployment, environments, access requirements
- "Process": development workflow, release process, code review norms
- "Technical Debt": areas that seem intentionally incomplete or in transition
- Each question: specific, actionable, with context about why it matters
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 · 69 lines · 86 tokens per session scan A b4cb9a4e520e
onboarding-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 861 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.