Borrowing it
Nothing to install: this file belongs to vladm3105/aidoc-flow-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vladm3105/aidoc-flow-framework/dev/.agents/skills/ship-it/SKILL.mdgit clone --depth 1 https://github.com/vladm3105/aidoc-flow-frameworkWrote 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/vladm3105/aidoc-flow-framework/ship-it)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/ship-it"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/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/vladm3105/aidoc-flow-framework/ship-it"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/ship-it.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.00051 | $0.02196 |
| Opus 5.5 | $0.00020 | $0.00878 |
| Sonnet 5.5 | $0.00010 | $0.00439 |
| Haiku 4.5 | $0.00005 | $0.00220 |
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 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship it
Muse project-skill instance of
ship-it— engine-agnostic wording mirrorsframework/skills/ship-it/SKILL.md. Canon source:aidoc-flow-claude-agents-config/skills/ship-it/SKILL.md. Where the canon names a Claude-specific agent type, use your engine's focused read-only subagent equivalent and keep the independence contract.
The stretch between "PR is open" and "PR is merged" had no owner: wrap-session
starts after the merge, and the skill that gets you to the PR stops at
opening it. This is that stretch, and nothing else.
0. Precedence, and one seam worth knowing
| File | Owns | Beats |
|---|---|---|
<repo>/CLAUDE.md |
the authorization and declaration — whether agents may auto-merge, merge convention, protected branches, who may merge | global defaults |
| the owning repo's AGENTS.md/CLAUDE.md | global safety carve-outs | this skill |
| this skill | the mechanism — how to watch, what "green" means, how to merge | — |
If this file and the owning repo's AGENTS.md/CLAUDE.md disagree, the policy wins and the
disagreement is a defect here.
The seam with superpowers:finishing-a-development-branch. That skill's
rationalization table says "Integration is your human partner's decision.
Present the menu and wait." It is not in conflict with merge-on-green — it
governs a different moment:
| Moment | Governed by |
|---|---|
| implementation done; choose an integration route (merge locally / open a PR / leave it) | finishing-a-development-branch — present the menu, wait |
| a PR of yours is open and its checks are running | the repo's explicit auto-merge rule, if any — otherwise wait for user direction |
Read them as sequential, not competing. Merge-on-green does not authorize merging locally without a PR — it presupposes an open PR and passing required checks. Do not use this skill to skip the menu.
1. Watch the checks
Read mergeStateStatus first — before any check rollup. It is the only field
that sees a missing required review: BLOCKED ends the question regardless
of what the checks say, and no check-rollup field reports it.
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 · 171 lines · 51 tokens per session scan A e7e2d8a5eef2
ship-it is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 2,196 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-28.
Other skills, from other repositories
emerging-techniques-model-merging
Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task…
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
release-safety
Release safety rules. INVOKE WHEN: yarn release, npm publish, release canary, release packages, publishing, skip checks, skip tests. NEVER skip checks or tests without explicit permission.