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 instructions/acaprino/daodan/agents-mdgit 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/instructions/acaprino/daodan/agents-md)<a href="https://agentmods.dev/instructions/acaprino/daodan/agents-md"><img src="https://agentmods.dev/badge/instructions/acaprino/daodan/agents-md.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.11358 | $0.11358 |
| Opus 5 | $0.05679 | $0.05679 |
| Sonnet 5 | $0.02272 | $0.02272 |
| Haiku 4.5 | $0.01136 | $0.01136 |
Grade A, and why
daodan AGENTS.md 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- daodan CLAUDE.md — 94% identical, 20 lines differ
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daodan
The Daodan is the symbiote that augments its host. This repository is the Daodan of coding agents: one marketplace of agents, skills, and workflows that augment a base model into a specialized toolkit covering development workflows, code quality, AI tooling, scraping, trading, observability, and more. It ships to three hosts from one source. Remote: acaprino/daodan on GitHub.
Project structure
plugins/<name>/ is a plugin's content kernel, and it is the only hand-authored plugin source alongside adapters/. Each kernel holds plugin.toml (the neutral control plane), roles/ (agent bodies), workflows/ (entry-point bodies plus one TOML sidecar each), skills/, contracts/ and policies/. Markdown is always the behaviour; TOML is always declarative metadata and never carries a prompt.
adapters/<host>/ is what one host can do: capabilities.toml binds every neutral capability to a host mechanism, coordination.toml orders the coordination strategies that host supports, layout.toml says where each component lands in its packages, templates/ holds the harness wrappers, policies/ holds this host's implementation of a neutral policy, and overrides/ holds fingerprinted semantic divergences.
Everything under exports/ and all three root marketplace manifests are generated. scripts/daodan_build.py compiles kernels plus adapters into exports/claude/, exports/copilot/ and exports/codex/, and into .claude-plugin/marketplace.json, .github/plugin/marketplace.json and .agents/plugins/marketplace.json. Never hand-edit them; edit the kernel and rebuild.
AGENTS.md and the four repository workflow skills under .agents/skills/ are native Codex adaptations of this file and .agents/skills/. Generate them with python scripts/sync_codex_instructions.py; --check is the parity gate. Edit the Claude-side canonical copies, then run the synchronizer. The transformation is deliberately limited to instruction paths, cache paths, install commands and the host-relative downstream description.
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 · 247 lines · 11,358 tokens per session scan A fb7088268526
daodan AGENTS.md is an instructions file published in the GitHub repository acaprino/daodan (8 stars, last pushed 8d ago), licensed MIT. It adds 11,358 tokens to every session, about $0.0568 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.