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 ship-itemgit 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/ship-item)<a href="https://agentmods.dev/skills/evolvehq/docflow/ship-item"><img src="https://agentmods.dev/badge/skills/evolvehq/docflow/ship-item/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/ship-item"><img src="https://agentmods.dev/badge/skills/evolvehq/docflow/ship-item.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.00083 | $0.02595 |
| Opus 5.5 | $0.00033 | $0.01038 |
| Sonnet 5.5 | $0.00017 | $0.00519 |
| Haiku 4.5 | $0.00008 | $0.00260 |
Grade A, and why
ship-item 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 1mo 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ship-item
Complete one queue item in the order required by the repository. Prepared completion on an unmerged PR is ready, not shipped. Never infer merge authorisation from a request to prepare or update the PR.
Context and selection
Read AGENTS and CONVENTIONS for integration branch/remote, gate, coordination
mode, signing, trailers and guardrails. Resolve adr/, plan/, INDEX.md
and _agent/ against the recorded root. Select the named item, otherwise
the lowest eligible one, and read its owning decisions and criteria in full.
Require Accepted ownership before preparing completion. If a linked PR
already contains the completion move, verify that prepared state instead
of repeating the move or rejecting its prepared Implemented status.
Inspect worktree cleanliness and item ownership. Preserve unrelated edits.
Only finish the named item; never repair unrelated decisions or accept
Proposed ones to make the gate pass. A literal branch named claim, an
invalid item key, or a source with no matching item is not a valid claim.
Validate branch names with git check-ref-format --branch.
Choose the mode
- Integrating mode: a named
claim/<item-key>under separate-worktree direct integration. Read the item from its fetched remote tip. Use the detached integration procedure below, never an executor or operator tree. - Default direct mode: verified work already on the integration branch, or an ordinary work branch that can safely fast-forward into its clean integration checkout. Shared-checkout work stays sequential in that tree.
- PR mode: use the actual PR branch. A single writer uses an ordinary work branch, not an invented claim ref. Shared-checkout ordinary PR work serialises the whole checkout; shared-checkout PR waves are unsupported.
Default direct completion
- Fetch/prune and confirm the integration base and source. Run the gate and require exit zero. If needed, fast-forward the verified work branch into the clean integration checkout without moving a branch held by another worktree. Do not push yet. If safe integration is unavailable, stop with the precise blocker rather than changing another checkout.
- Where guardrails are recorded, run audit/collision checks. Reconcile only the item's new unmerged numbers and references; regenerate INDEX.
- Prepare the atomic completion as described below. Run the gate again after the completion commit. Push the integration branch normally.
- Confirm the intended tip is on the remote. Only then report shipped and perform applicable cleanup. A rejected or uncertain push is not shipped; preserve local commits and report the remote state.
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.
- 1mo ago Changed · +11 lines b929994d4bf1
- 1mo ago Changed · +89 lines 20891d33bbba
- 1mo ago Changed · +31 lines · -4 tokens per session 85a2bfeda552
- 1mo ago Changed · +3 lines · -9 tokens per session ce3cea5b65ff
- 1mo ago First seen · 72 lines · 96 tokens per session scan A f22d1f92cc5a
ship-item is a skill published in the GitHub repository EvolveHQ/docflow (16 stars, last pushed 3d ago), licensed MIT. It adds 83 tokens to every session and 2,595 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-08-31.
Other skills, from other repositories
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
release-notes
Compare the repository with the team's Folio wiki and write release notes: read git log since the last tag, read the Roadmap table, create or update a Release notes page and add what the roadmap table is missing. Use when asked for release notes or to sync the wiki with the code.
atomic-issues-prs
Use when the user says "atomic PRs" or requests one issue or PR per logical change. Don't use for single-change pushes or uncommitted change-sets.
post-merge-cleanup
Use when a landed merge, release, or completed change needs its cleanup surface reconciled. Scans for stale TODOs, deprecations, unused flags, and doc gaps. Not for unrelated refactoring.
changelog
Record shipped work in the monthly changelog (append-only). Use when something ships or when asked "what changed", "add to changelog", "release notes", or "what shipped this month".
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.