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 hamzaPixl/pixl-ai --skill ship-milestonegit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/ship-milestone)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/ship-milestone"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/ship-milestone/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/hamzapixl/pixl-ai/ship-milestone"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/ship-milestone.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.00061 | $0.00866 |
| Opus 5.5 | $0.00024 | $0.00346 |
| Sonnet 5.5 | $0.00012 | $0.00173 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
ship-milestone 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Ship a body of work from analysis through implementation, testing, documentation, and release. Orchestrates the full lifecycle: assess what exists, plan what remains, implement in parallel, test as a user, update all docs, commit in logical groups, and push.
Read references/workflow.md for the detailed phase checklist.
Step 1: Assess Current State
Parse the input (spec file, architecture analysis, or description) to build a gap inventory.
- Read the spec/analysis document
- Launch Explore agents to deep-scan what is actually implemented vs. what the doc claims
- Reassess each item — real completion is often higher than documented
- Produce a revised status table: done / partial / not started / dropped
Output: Status table with accurate completion percentages.
Step 2: Plan Remaining Work
Use /task-plan methodology for remaining items:
- Group work into vertical slices (each delivers testable value)
- Size tasks (S < 1hr, M = 1-3hr)
- Split any L tasks
- Map dependencies and identify parallel groups
- Determine wave execution order
Output: Task list with IDs, sizes, dependencies, and wave assignments.
Step 3: Implement (Parallel Waves)
Execute implementation wave by wave:
- Start all independent tasks in Wave 1 simultaneously
- Use background agents for test-heavy or cross-boundary tasks
- Handle engine/CLI/infra changes directly for surgical edits
- Mark tasks complete as they finish
- Run
make test(or equivalent) after each wave to catch regressions - Start Wave 2+ only after dependencies from prior waves complete
Step 4: User-Flow Testing
Test every feature as documented in USAGE.md (or equivalent user guide):
- Run
--helpfor every new command group - Test CRUD cycles (create → list → get → update → delete)
- Test JSON output mode (
--json) - Test error paths (missing config, connection refused, invalid input)
- Test streaming/real-time features if applicable
- Verify simulated/dry-run modes work
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 First seen · 93 lines · 61 tokens per session scan A 464d4e8b47e5
ship-milestone is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 866 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-pause-work
Create context handoff when pausing work mid-phase.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
gait-session-tracking
GAIT session lifecycle management - branch creation, turn recording, audit logging for every NetClaw operation. Use when starting a new NetClaw session, recording a health check or config change, pinning a pre-change baseline, or viewing the audit trail for a troubleshooting session.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.