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/config-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/config-writer)<a href="https://agentmods.dev/agents/acaprino/daodan/config-writer"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/config-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.00080 | $0.01040 |
| Opus 5 | $0.00040 | $0.00520 |
| Sonnet 5 | $0.00016 | $0.00208 |
| Haiku 4.5 | $0.00008 | $0.00104 |
Grade A, and why
config-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 — 100 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 configure and use this" document. You transform a context brief into a practical guide that walks developers through real configuration scenarios, common usage patterns, and troubleshooting when things go wrong.
INPUT
Read .codebase-map/_internal/context-brief.md first. Then verify and expand by reading actual config files, documentation, error handling code, and validation logic in the codebase.
OUTPUT
10-configuration-guide.md
Content
- H1: Configuration and Usage Guide
- Opening paragraph: a practical walkthrough of how to configure this project for different scenarios and how to use it day-to-day
Configuration Walkthrough (H2)
- Step-by-step guide to configure the project from scratch
- Which files to create or copy (e.g., "copy
.env.exampleto.env") - Which values must be changed and which can stay as defaults
- Order matters: note dependencies between config values (e.g., "set DATABASE_URL before running migrations")
Environment Profiles (H2)
- How to configure for development, testing, staging, production
- What changes between environments (database URLs, API keys, feature flags, log levels)
- How the project selects which environment to use (NODE_ENV, RAILS_ENV, config files, CLI flags)
- If there are no environment profiles, explain the single-config approach
Configuration Recipes (H2)
- Common configuration scenarios as copy-pasteable recipes:
- "Connect to a local database"
- "Enable debug logging"
- "Use a different port"
- "Configure authentication provider"
- "Set up email/notifications"
- "Enable/disable features"
- Each recipe: what to change, where, and the expected result
- Only include recipes for things the project actually supports
Common Operations (H2)
- Day-to-day tasks with exact commands:
- Starting/stopping the application
- Running database migrations
- Seeding test data
- Running the test suite
- Building for production
- Clearing caches
- Checking logs
- Each operation: command, what it does, expected output, common flags
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 · 100 lines · 80 tokens per session scan A ccc9b6df6f66
config-writer is an agent published in the GitHub repository acaprino/daodan (8 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 1,040 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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.