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 bootstrapgit 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/bootstrap)<a href="https://agentmods.dev/skills/evolvehq/docflow/bootstrap"><img src="https://agentmods.dev/badge/skills/evolvehq/docflow/bootstrap/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/bootstrap"><img src="https://agentmods.dev/badge/skills/evolvehq/docflow/bootstrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 161 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00114 | $0.12212 |
| Opus 5.5 | $0.00046 | $0.04885 |
| Sonnet 5.5 | $0.00023 | $0.02442 |
| Haiku 4.5 | $0.00011 | $0.01221 |
Grade A, and why
bootstrap 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 9d 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 — 860 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bootstrap
You are installing (or retrofitting) a documentation-led convention set in the current repo. The end state is a repo that can be driven by both humans and coding agents off a small set of canonical files. Carry over the mechanism described here — nothing about any other project.
Step 1 — Detect the situation
Inspect the repo before asking anything. Reuse explicit answers and sign-off already supplied in this session; never replace them with profile defaults or ask for them again. Before writing, summarise the resolved artefact root, depth, queue, gate and coordination/integration modes against those answers. If a host mirrors a selected folder into a sandbox, identify the actual target path and how verified outputs reach the selected folder; never call an untouched target complete merely because a scratch mirror passed.
- Fresh repo (no source, no docs): you are scaffolding from zero.
- Existing repo: you are retrofitting.
- Read any current
README.md,CONTRIBUTING.md,AGENTS.md,CLAUDE.md,docs/,adr/,.github/before proposing changes. - Preserve existing content. Merge, don't overwrite. If existing conventions conflict with the ones below, surface the conflict in your assessment summary.
- If ADRs already exist in another format, propose a migration plan (renumber, keep, translate) rather than creating a parallel tree.
- Read any current
- Already a docflow repo (carries
AGENTS.md+CONVENTIONS.md+ an ADR catalogue): you are adding to an existing setup, not scaffolding. Do not re-scaffold the core or re-ask settled questions — read the recorded choices fromCONVENTIONS.md/AGENTS.md(ADR shape, status lifecycle, artefact root, multi-agent mode, and which optional layers already exist). Then offer to enable any opted-out optional layer still absent —plan/,_agent/,GLOSSARY.md,domains/, or the second ADR shape (the technology template) — and write only the chosen ones, by merge, under the recorded artefact root, leaving everything else untouched. Ask only the questions the new layers need (e.g. the coordination question when enabling_agent/— where a single writer without both a recorded verify gate and a plan queue correctly ends up with no_agent/at all, and the layer is simply not needed). This is the entry point for adding a layer you deferred at first bootstrap. A repo still carrying coordination files an earlier scaffold wrote keeps them: leave them in place here and let the audit skill report the layout.
What ships with it
43 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.
- agents/openai.yaml 302 B
- templates/_agent-LOCKS.md 985 B
- templates/_agent-prompts-autonomous.md 9.8 KB
- templates/_agent-ROLES.md 871 B
- templates/adr-0001-seed.md 5.4 KB
- templates/adr-capability.md 1.3 KB
- templates/adr-technology.md 1.4 KB
- templates/AGENTS.md 12 KB
- templates/CLAUDE.md 11 B
- templates/CONVENTIONS.md 21 KB
- templates/federation-config.md 1.1 KB
- templates/federation-index.md 1.1 KB
- templates/GLOSSARY.md 636 B
- templates/plan-README.md 3.4 KB
- templates/workspace-AGENTS.md 231 B
- templates/workspace-assets.json 465 B
- templates/workspace-brief.json 1.6 KB
- templates/workspace-CONVENTIONS.md 228 B
- templates/workspace-decisions.md 1012 B
- templates/workspace-grant.json 1.0 KB
- templates/workspace-ideas.md 908 B
- templates/workspace-INDEX.md 285 B
- templates/workspace-knowledge.md 1.3 KB
- templates/workspace-mandate.md 860 B
- templates/workspace-profile-coordination.md 576 B
- templates/workspace-profile-documentation.md 580 B
- templates/workspace-profile-react-review.md 582 B
- templates/workspace-profile-svelte-tauri.md 618 B
- templates/workspace-profile.md 418 B
- templates/workspace-README.md 365 B
- templates/workspace-receipt.json 955 B
- templates/workspace-recommendation.json 533 B
- templates/workspace-registry.yaml 170 B
- templates/workspace-role-coordinator.md 1.3 KB
- templates/workspace-role-domain-specialist.md 1.4 KB
- templates/workspace-role-executor.md 1.3 KB
- templates/workspace-role-reviewer.md 1.3 KB
- templates/workspace-role.md 577 B
- templates/workspace-run-import.md 1.6 KB
- templates/workspace-runs.md 2.7 KB
- templates/workspace-sources.yaml 956 B
- templates/workspace-starter-sources.yaml 3.6 KB
- templates/workspace-work.md 1.3 KB
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.
- 9d ago Changed · +23 lines 35ca8f9609e1
- 1mo ago Changed · +44 lines 105357bfd3e3
- 1mo ago Changed · +48 lines 9edf451be964
- 1mo ago Changed · +9 lines · -4 tokens per session 4c5b759b028a
- 1mo ago Changed · +82 lines 47445c3ab73b
- 1mo ago Changed · +43 lines 5a1e5b400e77
- 1mo ago First seen · 611 lines · 118 tokens per session scan A 4dcb8b7cb637
bootstrap is a skill published in the GitHub repository EvolveHQ/docflow (16 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 12,212 once invoked, about $0.0005 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-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.
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".