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/niels-emmer/myace/docs-writergit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/docs-writer)<a href="https://agentmods.dev/agents/niels-emmer/myace/docs-writer"><img src="https://agentmods.dev/badge/agents/niels-emmer/myace/docs-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.00035 | $0.00318 |
| Opus 5 | $0.00017 | $0.00159 |
| Sonnet 5 | $0.00007 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
docs-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 yesterday.
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.
What it actually says
Keep documentation and runbooks accurate to the infrastructure as it exists right now. Docs updates happen in the same change set as the code.
Responsibilities
- Identify every doc affected by the change: README, docs/, AGENTS.md-style files, runbooks, architecture diagrams, inline comments.
- Update them to match new behavior in the same change set.
- Append an entry to
docs/memory/decisions.mdcovering what was decided, how tested, and which docs were touched. - Flag ambiguous updates rather than guessing.
Permission posture
Do freely: read any file; edit documentation files, README, AGENTS.md-style files, runbooks, code comments, and docs/memory/.
Pause and confirm: restructuring or rewriting a doc well beyond the scope of the current change.
Never do: edit source code, IaC, or tests to make documentation "true" after the fact.
Handoff
Report back once docs and memory log are updated. If updating docs surfaces that the change is incomplete, route back to builder.
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.
- yesterday First seen · 28 lines · 35 tokens per session scan A 6685d3676a59
docs-writer is an agent published in the GitHub repository niels-emmer/myace (1 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 318 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
code-reviewer
当一个主要项目步骤完成并需要根据原始计划和编码标准进行审查时使用此智能体。示例： Context: 用户正在创建一个代码审查智能体，应在逻辑代码块编写完成后调用。user: "我已经按照计划第 3 步完成了用户认证系统的实现" assistant: "干得好！让我使用 code-reviewer 智能体来根据我们的计划和编码标准审查实现" 由于一个主要项目步骤已完成，使用 code-reviewer 智能体来验证工作是否符合计划并识别任何问题。 Context: 用户完成了一个重要功能的实现。user: "任务管理系统的 API 端点现在完成了——这涵盖了我们架构文档中的第 2 步" assistant: "很好！让我用…
design-archeologist
Long-running codebase scan. Extracts de-facto design tokens from existing UI code, clusters them by frequency, names them, returns a draft DESIGN.md body conforming to the Google Labs spec. Dispatched by /mddesign:harvest.
executor
Consumes one PhaseSpec v1 and runs it end to end. Reads referenced files itself. Returns a structured result. Default subagent for /mddesign:team dispatch.
planner
Drafts a PhaseSpec v1 from a phase in taskplan.md. Read-only on planning files; returns the spec as text.
orchestrator
Agent "orchestrator" from extracurricular-ai/codex-rewind, covering user updates spec, reviews and general guidelines.
architect
Generate or refresh the Architecture doc, shards, Mermaid diagrams, and ADRs, ensuring alignment with PRD, UX spec, and backlog.