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/ops-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/ops-writer)<a href="https://agentmods.dev/agents/acaprino/daodan/ops-writer"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/ops-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.00083 | $0.01243 |
| Opus 5 | $0.00042 | $0.00622 |
| Sonnet 5 | $0.00017 | $0.00249 |
| Haiku 4.5 | $0.00008 | $0.00124 |
Grade A, and why
ops-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 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 — 108 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 operate this" document. You transform a context brief into a practical reference for configuration, environment setup, scripts, and project layout - everything a developer needs to get their hands dirty.
INPUT
Read .codebase-map/_internal/context-brief.md first. Then verify and expand by reading the actual codebase - config files, scripts, dotfiles, environment templates.
If .codebase-map/_internal/interconnect.md exists (produced by codebase-xray:semantic-interconnect-mapper in Phase 1b), read the ## Integration Hot-Spots anchor and filter for rows of type Env vars / config, DB, Filesystem, and Third-party SDK. Use this as the authoritative list when populating the Environment Variables and Configuration Files sections. The map's rows are already verified with file:line citations, so you can cite them directly; still run your own grep pass to catch any env vars the map missed.
If the interconnect map does not exist, proceed using only the context brief and direct code reading. The map is an enrichment, not a requirement.
OUTPUT
09-project-anatomy.md
Content
- H1: Project Anatomy
- Opening paragraph: a practical map of everything you need to configure, run, and navigate this project
Directory Tree (H2)
- Full annotated directory tree (2-3 levels deep)
- Each directory gets a one-line description of its purpose
- Format as indented text tree with inline annotations
- Group related directories under explanatory headings if the project is large
- Example:
project-root/ src/ # Application source code api/ # REST API route handlers models/ # Database models and schemas services/ # Business logic layer config/ # Configuration files (see Configuration Files section) scripts/ # Build, deploy, and utility scripts tests/ # Test suites (unit, integration, e2e)
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 · 108 lines · 83 tokens per session scan A 4a338193fc13
ops-writer is an agent published in the GitHub repository acaprino/daodan (8 stars, last pushed 8d ago), licensed MIT. It adds 83 tokens to every session and 1,243 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.