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 skills/evolvehq/docflow/rollupnpx skills add EvolveHQ/docflow --skill rollupgit clone --depth 1 https://github.com/EvolveHQ/docflowWhat 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.00109 | $0.00949 |
| Opus 5 | $0.00055 | $0.00475 |
| Sonnet 5 | $0.00022 | $0.00190 |
| Haiku 4.5 | $0.00011 | $0.00095 |
Grade A, and why
rollup 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 2d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rollup
Aggregate the ADR catalogues of every repo in a multi-repo product into
one derived, read-only product-wide view. The roll-up is regenerated
from source, never hand-edited — treat it exactly like a repo's own
INDEX.md.
Step 0 — Preconditions
- This skill runs in the index-holding repo of a federation — the one
that carries
federation-index.md(itsRoleiscentralfor topology A,coordinatorfor B, orhomefor C). Confirmfederation-index.mdand afederation.mdwhoseRoleiscentral,home, orcoordinatorexist. If they do not, stop: either this repo is standalone (nothing to roll up) or it is a plain member — point the user at the index-holding repo. - Read
federation.mdto learn the identity scheme (default repo-prefixed slug<repo-id>/NNNN-slug); roll-up rows use it.
Step 1 — Enumerate members
Read federation-index.md. For each row, take the Repo id and the
Pointer (the path/URL of that member's checkout). The member index is
the only source of membership — do not auto-discover repos.
Step 2 — Collect each member's catalogue
For every member whose checkout is locally available at its pointer:
- Read that member's
INDEX.md(its authoritative local catalogue). - For each ADR row, capture the number, title, status, date, and dependencies, and attach the owning repo id and the federation identity (the scheme from Step 0 applied to the local number).
A member's own INDEX.md stays authoritative for that member; this skill
only reads it.
For the aggregate status of a product-wide decision (one with owning
per-repo plan items across several members), also scan each member's
plan/todo/ (pending) and plan/done/ (shipped) for items naming that
decision's federation identity — that per-repo state feeds the aggregate
column in Step 4.
Step 3 — Handle unreachable members
A member named in the index whose checkout is not locally available is not dropped and not a failure. Record it in a clearly separated "Not aggregated this run" list with its repo id and pointer, so the gap is visible rather than silent.
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.
- 2d ago First seen · 79 lines · 109 tokens per session scan A b4c7c7cc939b
rollup is a skill published in the GitHub repository EvolveHQ/docflow (10 stars, last pushed 27d ago), licensed MIT. It adds 109 tokens to every session and 949 once invoked, about $0.0005 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 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-format-structured-madr
This skill should be used when the user asks about "structured MADR", "structured-madr", "frontmatter ADR", "comprehensive ADR", "auditable ADR", or needs guidance on creating ADRs using the Structured MADR format with YAML frontmatter and audit sections.
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-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.
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.