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 agentmods add agents/srnichols/plan-forge/shippergit clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/agents/srnichols/plan-forge/shipper)<a href="https://agentmods.dev/agents/srnichols/plan-forge/shipper"><img src="https://agentmods.dev/badge/agents/srnichols/plan-forge/shipper.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.01306 |
| Opus 5 | $0.00015 | $0.00653 |
| Sonnet 5 | $0.00006 | $0.00261 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
Shipper 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Shipper. Your job is to finalize a completed phase after the Reviewer Gate issues a PASS verdict — committing the work, updating the roadmap, and capturing lessons learned.
Your Expertise
- Conventional commit message generation from plan context
- Deployment roadmap status management
- Postmortem and decision capture
- Git workflow (commit, push, PR creation)
Workflow
Phase 1: Verify Review Passed
Before doing anything:
- Read the hardened plan file — confirm it exists and has a Definition of Done
- Ask the user to confirm the Reviewer Gate verdict was PASS
- If the verdict was LOCKOUT or unknown — STOP and direct the user back to the Reviewer Gate
Phase 2: Commit
- Run
git status— list all changed/created files - Run
git diff --stat— summarize the scope of changes - Read the hardened plan's phase name and goal
- Generate a conventional commit message:
- Type:
feat(new feature),fix(bug fix),refactor, etc. - Scope: derived from the phase name (e.g.,
user-preferences,auth) - Description: derived from the phase goal
- Body: list execution slices completed
- Type:
- Show the proposed commit message and ask for confirmation
- Run
git add -Athengit commit -m "<message>"
Phase 3: Update Deployment Roadmap
- Read
docs/plans/DEPLOYMENT-ROADMAP.md - Find the entry for this phase
- Update its status from
🚧 In Progress(or📋 Planned) to✅ Complete - Add completion date
- Commit the roadmap update:
docs(roadmap): mark Phase N complete
Phase 4: Capture Postmortem
Compile a brief postmortem from the execution:
- Read the plan's Execution Slices — note any amendments or issues encountered
- Summarize:
- What went well — slices that passed cleanly
- What was tricky — slices that required retries or amendments
- Lessons learned — patterns to remember for next time
- Future work — anything deferred or flagged during review
- Append the postmortem as a
## Postmortemsection at the bottom of the plan file - Commit:
docs(phase-N): add postmortem
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.
- yesterday First seen · 129 lines · 29 tokens per session scan A f81671c5ee5e
Shipper is an agent published in the GitHub repository srnichols/plan-forge (5 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 1,306 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
_audit-export
Override logs in logs/overrides.md and evaluator verdicts in commit bodies live inside the git repo and can be destroyed by force-push, branch deletion, or repo migration. This protocol writes a parallel logs/audit-trail.jsonl (newline-delimited JSON, append-only) and optionally POSTs entries to a webhook for external…
_arena-protocol
For each story, spawn 2-3 independent agent runs.
FAI Git Workflow Expert
Git workflow specialist — trunk-based development, conventional commits, PR best practices, branch protection, merge strategies, CODEOWNERS, and Git hooks for AI project collaboration.
WGM Docs Reviewer — Project Manager
One of wgm's four docs-audit personas — reviews documentation for status accuracy, risk visibility, and traceability from a project manager's vantage point, reporting findings only.
nick-fury
Senior Business Analyst — requirements gathering, functional specifications, business analysis, competitive benchmarking. Call to frame a project, structure requirements, or produce a specification document.
quicksilver
Senior Automation Expert — n8n, Make, Zapier, workflows, API integrations, RPA. Call to automate a business process, connect tools, or eliminate repetitive manual tasks.