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 workspace-setupgit 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/workspace-setup)<a href="https://agentmods.dev/skills/evolvehq/docflow/workspace-setup"><img src="https://agentmods.dev/badge/skills/evolvehq/docflow/workspace-setup/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/workspace-setup"><img src="https://agentmods.dev/badge/skills/evolvehq/docflow/workspace-setup.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.00052 | $0.01559 |
| Opus 5.5 | $0.00021 | $0.00624 |
| Sonnet 5.5 | $0.00010 | $0.00312 |
| Haiku 4.5 | $0.00005 | $0.00156 |
Grade A, and why
workspace-setup 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
workspace-setup
Establish the operator-selected canonical workspace home.
Operating contract
Inputs: selected destination, new/adopt choice, purpose, canonical home, member identities/paths, owner, native host and write scope. Effects: create or merge only the agreed workspace files and ignores; initialise its Git history only when authorised. Cloning/registering members is a separate named effect. Never implicitly convert a parent container. Native claims / dependencies / resources: confirm ownership of the destination and any shared configuration; require explicit member access before registration validation. No member execution is assigned. Stopping point: a validated, inspectable workspace with a dated overview, or a concrete missing-input/asset/ownership blocker. Receipt: paths created/merged, preserved files, package revision, actual validation command/output/exit, unresolved members, host availability and next action. Do not create a fictitious run for setup without a work/grant.
Resolve inputs and current authority
Reuse applicable choices already supplied, including host, actor, paths, scope, depth and stopping point. Summarise the resolved choices; ask only for a material missing or conflicting choice. A recorded preference alone does not supply authority. Selection sets priority; accepted agreement, role, profile, registry membership and a copied brief grant no execution.
Locate the installed sibling bootstrap skill (resolve symlinks first).
Its templates/workspace-assets.json lists the packaged asset locations:
../../workspace in a plugin or ../../docflow-workspace in a detached
copy, relative to bootstrap. An explicit asset root is valid. Read that
root's CONTRACT.md, schema.json and README.md; all templates are
in bootstrap's templates/. If missing, report the exact missing asset
and stop dependent writes. Never assume a source checkout or install/fetch
dependencies implicitly. The external validator requires Node.js 22+.
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.
- 9d ago First seen · 123 lines · 52 tokens per session scan A 5c1e4b55fd9c
workspace-setup is a skill published in the GitHub repository EvolveHQ/docflow (16 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,559 once invoked, about $0.0002 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-07.
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.
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.