Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mickeyyaya/evolve-loopnpx agentmods add skills/mickeyyaya/evolve-loop/docs-writeWrote 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/skills/mickeyyaya/evolve-loop/docs-write)<a href="https://agentmods.dev/skills/mickeyyaya/evolve-loop/docs-write"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/docs-write/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mickeyyaya/evolve-loop/docs-write"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/docs-write.svg" alt="Reviewed on agentmods" width="80" 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.00081 | $0.01893 |
| Opus 5.5 | $0.00032 | $0.00757 |
| Sonnet 5.5 | $0.00016 | $0.00379 |
| Haiku 4.5 | $0.00008 | $0.00189 |
Grade A, and why
docs-write 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-write — documents that a person reads to learn and to decide
A document in this repository has two readers. A person reads it to understand the system and to judge a decision. An agent reads it to do work. Write for the person first. If a person can follow the reasoning and check each claim, an agent can too.
Sources of this skill: docs/research/docs-write-skill-2026-10.md. House rules: docs/conventions/ste100-writing.md and docs/conventions/markdown-structure.md.
The five laws
- One document has one type and one home. Choose the type before you write (table below). Do not mix a how-to into a design, or a decision into a research dossier.
- Every claim has a source. A local claim cites
path:line, a command and its output, or a measured number with its date. An outside claim cites a link. Your own inference says "synthesis". - Every decision shows its reasoning. Write the chain: fact → implication → decision → consequence. Show the alternatives that you rejected and why. A decision without its reasons is an order, not a design.
- Teach before you specify. Give the reader the context, the terms and one worked example before the rules. A new reader must finish with the mental model, not only the list.
- The text is checkable. Run
evolve docs ste-lint --strict --changed <base> --addedand the link check before you hand off. A document that fails its checks is not done.
Choose the type and the home
| Type | Question it answers | Home | Template |
|---|---|---|---|
| Research dossier | What did we find, and what does current practice say? | docs/research/<topic>-<yyyy-mm>.md |
references/templates.md §Research |
| Plan | What will we build, in which order, and how do we prove it? | docs/plans/<topic>-<yyyy-mm>.md |
references/templates.md §Plan |
| Decision record (ADR) | What did we decide, and why? | docs/architecture/adr/<nnnn>-<decision-as-a-sentence>.md |
references/templates.md §ADR |
| Architecture spec | How does this part of the system work? (the spec of record) | docs/architecture/<topic>.md |
references/templates.md §Architecture |
| Convention | Which rule must every author follow? | docs/conventions/<rule>.md |
references/templates.md §Convention |
| How-to or operations guide | How do I do this task? | docs/operations/ or docs/guides/ |
references/templates.md §How-to |
| Concept primer | What is this, for a new reader? | docs/concepts/ |
references/templates.md §Concept |
| Incident record | What broke, why, and what changed? | docs/incidents/<date>-<topic>.md |
references/templates.md §Incident |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +4 lines 145bf639f26f
- 13d ago First seen · 99 lines · 81 tokens per session scan A 93f48bd6476b
docs-write is a skill published in the GitHub repository mickeyyaya/evolve-loop (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 81 tokens to every session and 1,893 once invoked, about $0.0003 per session on Opus 5.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-10-12.
Other skills, from other repositories
incident
Incident response and postmortem generation from git/deploy context. When something breaks in production, this skill builds a timeline, identifies the probable cause, and generates a structured postmortem document. Flags: --since, --service, --sev, --revert, --comms, --dry-run.
presentation
Generate PowerPoint (PPTX) presentations from a topic, outline, or content file. Creates professional slides using python-pptx with consistent theming and typography. Modes: [topic] (from scratch), from [file] (from markdown), --slides N, --theme dark|light|corporate, --outline-only, --out [path], --lang [code].
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
deliverable-creation
Produce polished, consulting-quality deliverables including slide decks, reports, memos, and one-pagers. Use this skill when the user mentions: create a deck, build a presentation, make slides, write a report, executive summary, one-pager, synthesis, storyboard, slide structure, pyramid principle, consulting deck…
report-formats
Output formats and report templates for the research-team plugin's reports. The research-report-writer agent loads this skill for every report. It also applies when a user asks for a research report, technical survey, decision brief, landscape scan, what's-new digest or source summary in a particular editor's format…
vault-mirror
Use when you need to populate the Meta-Vault with machine-generated notes derived from session-orchestrator JSONL records. Converts entries from .orchestrator/metrics/sessions.jsonl and .orchestrator/metrics/learnings.jsonl into vault-conformant Markdown under 50-sessions/ and 40-learnings/. Called automatically at…