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 skills add EvolveHQ/docflow --skill new-adrgit clone --depth 1 https://github.com/EvolveHQ/docflowWrote 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/evolvehq/docflow/new-adr)<a href="https://agentmods.dev/skills/evolvehq/docflow/new-adr"><img src="https://agentmods.dev/badge/skills/evolvehq/docflow/new-adr/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/evolvehq/docflow/new-adr"><img src="https://agentmods.dev/badge/skills/evolvehq/docflow/new-adr.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.00147 | $0.02862 |
| Opus 5.5 | $0.00059 | $0.01145 |
| Sonnet 5.5 | $0.00029 | $0.00572 |
| Haiku 4.5 | $0.00015 | $0.00286 |
Grade A, and why
new-adr 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 11d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
new-adr
Author one new ADR, consistent with this repo's conventions.
Step 0 — Preconditions and context
- Confirm the repo is bootstrapped:
AGENTS.md,CONVENTIONS.md, and anadr/directory with at leastadr/0000-template.mdmust exist. If not, stop and offer to run the bootstrap skill first. - Read
CONVENTIONS.mdto learn this repo's choices: the ADR shape scheme — a single shape, or two shapes (capability and technology) declared by ashape:field in each ADR's metadata block; there is no number boundary to read — status lifecycle, language mandate (if any), whetherdomains/groupings exist (and, if so, which domain this ADR belongs to — ask if it isn't obvious), the multi-agent mode, and the artefact root (default: repository root) — resolveadr/andINDEX.mdagainst it (AGENTS.md/CLAUDE.mdstay at the repo root). Legacy range encoding. A repo scaffolded before the shape became a declared field encodes it in the number instead — §ADR Shapes records a cutoff, oradr/holds a template numbered other than0000(e.g.adr/0100-template.md); either signal alone identifies it. Say so, and offer the migration onto the declared field (the audit skill carries the procedure) before authoring. If the operator declines, author under the repo's own rules: read the cutoff and place this ADR on its side of it — capability below, technology at or above, next contiguous within that block — using the boundary-numbered template for a technology ADR, and write noshape:field, which that repo does not use. If the block this ADR belongs to has reached the cutoff, stop and say so: the range is full, and the remedy is the migration, never crossing the boundary. - Read
INDEX.mdandls adr/to learn existing numbers and titles. Ignore everyadr/0000-*.mdfile — the templates are not decisions and hold no number in the sequence. Under the legacy range encoding, ignore the boundary-numbered template the same way: it is a template, not the first technology ADR. - If a
federation.mdexists, this repo is part of a multi-repo product. Note the identity scheme and the home it records — they govern numbering and cross-repo references below.
What ships with it
1 file 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.
- 11d ago Changed · +7 lines 3b8ac8e05f48
- 1mo ago Changed · +3 lines 6ff3da714eb6
- 1mo ago Changed · +16 lines 834b3f4b338b
- 1mo ago Changed · +29 lines 25b5951bc078
- 1mo ago Changed · +14 lines 50751f09a250
- 1mo ago First seen · 141 lines · 147 tokens per session scan A 7940ebd8c2d0
new-adr is a skill published in the GitHub repository EvolveHQ/docflow (16 stars, last pushed 3d ago), licensed MIT. It adds 147 tokens to every session and 2,862 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
adr-integration
This skill should be used when the user asks about "ADR integration", "ADR CI/CD", "ADR tooling", "ADR automation", "export ADRs", "ADR documentation site", or needs guidance on integrating ADRs with CI/CD, documentation sites, and other tools.
adr-decision-drivers
This skill should be used when the user asks about "decision drivers", "architectural forces", "quality attributes", "how to identify trade-offs", "non-functional requirements for ADRs", or needs help identifying, documenting, and weighing the forces that influence architectural decisions.
adr-compliance
This skill should be used when the user asks about "ADR compliance", "architecture compliance", "ADR audit", "enforce ADRs", "check code against ADRs", "ADR violations", or needs guidance on auditing code compliance with accepted architectural decision records.
adr-fundamentals
This skill should be used when the user asks "what is an ADR", "when should I create an ADR", "ADR best practices", "architecture decision records", "ADR lifecycle", "how to document architecture decisions", or needs guidance on ADR fundamentals, when to create ADRs, or ADR lifecycle management.
adr-quality
This skill should be used when the user asks about "ADR quality", "review ADR", "ADR checklist", "improve ADR", "ADR validation", "good ADR examples", or needs guidance on evaluating, improving, and maintaining high-quality architectural decision records.
atlas-adr
Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".