agentmods.dev

ship-feature

A feature-closing command that marks a development plan complete and moves it into a dated archive after required checks pass.

In plain words
What is it for?
Use it after a feature’s pull request is merged, quality checks pass, and the working folder has no uncommitted changes.
Why use it?
It provides a consistent way to confirm that a feature is finished and keep completed plans organized.

Command for Claude Code

18 2mo ago A scan 33 tokens original MIT
View the source file pluginslab/wp-agentic-kit
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 commands/pluginslab/wp-agentic-kit/ship-feature
Clone the repo
git clone --depth 1 https://github.com/pluginslab/wp-agentic-kit

Made for: Claude Code.

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 379 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.00033 $0.00379
Opus 5 $0.00016 $0.00189
Sonnet 5 $0.00007 $0.00076
Haiku 4.5 $0.00003 $0.00038

Measured yesterday against content hash 6cd362296f5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ship-feature 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 yesterday.

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.

.claude/commands/ship-feature.md · 32 lines

What it actually says

Ship feature

Close the loop on a shipped feature.

  1. If $ARGUMENTS is empty, locate the active feature: the most recently modified .claude/plans/features/*/progress.md whose status: is not already complete. Use its directory's basename as the slug.
  2. If $ARGUMENTS is non-empty, use it as the slug. Verify the dir exists.
  3. Pre-flight checks (refuse if any fail):
    • The feature's PR is merged into main. Confirm with gh pr list --state merged --head feat/<slug> or ask the user if gh isn't available.
    • ./scripts/quality.sh exits clean against the current main.
    • Working tree is clean (no uncommitted changes).
  4. Update .claude/plans/features/<slug>/progress.md:
    • Set status: complete.
    • Append a final log entry: YYYY-MM-DD HH:MM — Feature shipped, archiving.
  5. Move the dir: 
    mv ".claude/plans/features/<slug>" \
   ".claude/plans/archive/$(date +%Y-%m-%d)-<slug>"
  6. Commit the archive move on main (or open a tiny PR if the project requires PRs for everything): 
    chore: archive plan for <slug>
  7. Report:
    • The archive path.
    • The merged PR URL.
    • Any open follow-up notes from findings.md worth turning into new features.
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. yesterday First seen · 32 lines · 33 tokens per session scan A 6cd362296f5a

Subscribe to this mod's changes

ship-feature is a command published in the GitHub repository pluginslab/wp-agentic-kit (18 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 379 once invoked, about $0.0002 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-30.

Code reviewPlanningagenticai-codingclaude-codemcpwordpress
Related

Other commands, from other repositories

respond-to-issue

Respond to an issue triggered by @elixpoo mention or the ELIXPO label.

elixpo/claudeOps.elixpo · 0 tokens

commit-push-pr

Commit, push, and open a PR. Branch rules prevent accidents on main or duplicate PRs.

elixpo/claudeOps.elixpo · 0 tokens

fill-pr-description

Generate a PR description from the diff. Triggered when a whitelisted author puts @elixpoo fill in the PR body.

elixpo/claudeOps.elixpo · 0 tokens

review

Command "review" from elixpo/claudeOps.elixpo, covering what to look at, don't, output format, issues and suggestions.

elixpo/claudeOps.elixpo · 0 tokens

dispatcher

Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.

Kanevry/session-orchestrator · 31 tokens

standup

Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.

skullninja/coco-workflow · 21 tokens