Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardnpx agentmods add skills/blackbelttechnology/pi-agent-dashboard/ship-itWrote 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/blackbelttechnology/pi-agent-dashboard/ship-it)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/ship-it"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/ship-it/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/blackbelttechnology/pi-agent-dashboard/ship-it"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/ship-it.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00092 | $0.03830 |
| Opus 5 | $0.00046 | $0.01915 |
| Sonnet 5 | $0.00018 | $0.00766 |
| Haiku 4.5 | $0.00009 | $0.00383 |
Grade A, and why
ship-it 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 10d 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ship-it
Orchestrates the implementation phase of an OpenSpec change inside its git
worktree. Twin of plan-proposal (which runs the planning phase on develop).
Composes existing skills — openspec-apply-change, the docker harness, and
ship-change — and adds the wiring they lack. Runnable headless.
flowchart LR
P["plan-proposal (develop)"] -->|"boundary: spawn worktree"| S
subgraph Worktree ["IMPLEMENTATION — worktree (this skill)"]
S["ship-it"] --> A["apply"] --> M["merge develop (2.5)"] --> T["docker-harness test"] --> E["enforcers (4.4)"] --> R["local review (4.5)"] --> C["ship-change"]
end
S -.->|"reverse: SHIP_IT_BLOCKED.md on design issue"| P
Pure decision logic lives in this skill's own scripts/ directory and is
unit-tested (.pi/skills/ship-it is a vitest project):
scripts/manifest.ts (parseManifest, deferDecision, filesystemRealityCheck),
scripts/no-weakening.ts (assertNoWeakening), and
scripts/review-gate.ts (reviewRoundDecision, resolveReviewer,
classifyFindings, REVIEW_TIMEOUT_MS).
Preconditions
- Running inside the change's worktree (
.worktrees/os-<change>, branchos/<change>). Resolve the change name from the worktree dir basename. dockeravailable (the e2e harness);openspecCLI resolves from the parent repo root when inside a worktree (perAGENTS.md).- Announce: "Shipping change:
<change>(worktree implementation phase)."
Procedure
1. Orient with openspec status, but gate on filesystem reality (idempotent)
Read openspec status --change <change> --json for orientation only. Do not
trust the tasks.md checkbox as proof an automated scenario is done — a
hand-checked or prior-partial - [x] can lie.
Parse test-plan.md (parseManifest). For each automated row, resolve its
folded test file and run filesystemRealityCheck: a scenario is satisfied only
when its test file exists AND passes in the harness (step 3). Any automated
row whose test file is absent → NOT done → author it (step 2) regardless of the
checkbox. This makes re-invocation genuinely idempotent: fresh run and re-run
reach the same all-green end state.
What ships with it
6 files 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.
- 10d ago First seen · 279 lines · 92 tokens per session scan A 7de55ed91748
ship-it is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (278 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 3,830 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-30.
Other skills, from other repositories
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…
akigitcommit
Analyze the working tree and commit changes in clean logical groups. Triages a long half-finished tree first (finished vs mid-edit vs abandoned vs accidental) before grouping. Auto-detects CHANGELOG to switch between domain-grouped mode (3–5 commits by object/feature) and type-grouped mode (feat/fix/refactor). Stages…
akidevsync-notes
Read and edit a project's .akidevsync/notes.json task/note file — the per-project task list written by the Aki-Dev-Sync app (github.com/lacvietanh/aki-dev-sync). Use when the user asks to list, add, pin/unpin, mark done, edit, or delete a task in that file, or mentions "task note", "note ghim", "pin task", "mark…
akiship
Full release ritual end-to-end — front-loaded checks, then an unattended pass. ACTIVATION IS LITERAL: this skill runs only on a user turn containing the exact token /akiship that asks for the run to be performed. Nothing else activates it — not the bare word "akiship", not a release-flavored paraphrase, and never a…
send-feedback
Explicit Codex workflow: Collect reviewed, sanitized rn-dev-agent feedback and create a GitHub issue only with user confirmation.
starfleet
Fleet coordination — comms, concurrency, task capture, and starfleetctl CLI. Load when handling inter-ship messages, setting up parallel work, capturing tasks, or running starfleetctl commands.