agentmods.dev

ship-item

A workflow skill for completing a planned documentation task in a repository and recording it as shipped.

In plain words
What is it for?
Use it to run the required verification, integrate the work, move its todo file to done, update decision records, and refresh repository indexes and logs.
Why use it?
It turns a finished plan item into a checked, integrated, documented repository change.

Skill for Claude CodeCodex

11 +1 27d ago A scan 96 tokens original MIT
View the source file EvolveHQ/docflow
Install

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.

agentmods
npx agentmods add skills/evolvehq/docflow/ship-item
Any agent
npx skills add EvolveHQ/docflow --skill ship-item
Clone the repo
git clone --depth 1 https://github.com/EvolveHQ/docflow

Made for: Claude Code, Codex.

Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 805 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00096 $0.00805
Opus 5 $0.00048 $0.00402
Sonnet 5 $0.00019 $0.00161
Haiku 4.5 $0.00010 $0.00081

Measured 2d ago against content hash f22d1f92cc5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

plugins/docflow/skills/ship-item/SKILL.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ship-item

Execute the completion event for one queue item. This is the most order-sensitive operation in the system — follow the steps exactly.

Step 0 — Preconditions and context

  1. Confirm the repo is bootstrapped with a plan/ queue.
  2. Read CONVENTIONS.md and AGENTS.md for: the integration model (direct-to-main fast-forward vs. PR-based with required CI), the verify gate command, the multi-agent mode, and the Git contract (signed commits, tags, trailers). Resolve adr/, plan/, and INDEX.md against the artefact root recorded in CONVENTIONS.md (default: repository root).

Step 1 — Select the item

Default to the lowest-numbered plan/todo/ file, or the one the user names. Read it and the owning ADR(s) in full.

Step 2 — Verify

Run the repo's verify gate. Require a pass. Do not bypass with --no-verify or equivalent. If it fails, stop, surface the failure, fix the root cause, re-run.

Step 3 — Integrate (per the repo's model)

  • Direct-to-main, fast-forward: git merge --ff-only <branch> (or the work is already on main), then git push origin main. The verify gate ran locally in Step 2.
  • PR-based: push the branch, gh pr create --draft --fill, wait for CI green (gh pr checks --watch), gh pr ready, then gh pr merge with the repo's strategy. Confirm the merge landed on main before continuing.

Step 4 — Move the queue item

Once the change is on main:

  • git mv plan/todo/NNNN-<slug>.md plan/done/<YYYY-MM-DD>-<slug>.md (today's date prefix).
  • Amend the moved file with a footer: "Shipped at HEAD <sha>" plus any artefact id, image tag, deploy id, or PR link.

Step 5 — Advance the ADR(s) and regenerate

  • Advance each owning ADR's status: from Accepted to Implemented.
  • Append a Revision History row if the status change is substantive (it is). Regenerate INDEX.md to match.

Step 6 — Record

If _agent/ was omitted at bootstrap (Q5 = None), skip this step — git history is the record.

Read the full file on GitHub · 72 lines

Files

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.

Changes

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.

  1. 2d ago First seen · 72 lines · 96 tokens per session scan A f22d1f92cc5a

Subscribe to this mod's changes

ship-item is a skill published in the GitHub repository EvolveHQ/docflow (11 stars, last pushed 27d ago), licensed MIT. It adds 96 tokens to every session and 805 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.

Data and AIGit and workflowWriting and docsadrarchitecture-decision-recordsclaude-codeclaude-code-plugindocumentation
Related

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.

zircote-plugins/adr · 59 tokens

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.

zircote-plugins/adr · 63 tokens

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.

zircote-plugins/adr · 60 tokens

adr-format-madr

This skill should be used when the user asks about "MADR format", "MADR template", "Markdown Architectural Decision Records", "MADR 4.0", "MADR sections", or needs guidance on creating ADRs using the MADR (Markdown Architectural Decision Records) format.

zircote-plugins/adr · 63 tokens

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.

zircote-plugins/adr · 68 tokens

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.

zircote-plugins/adr · 55 tokens