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 codecast-sh/codecast --skill cast-shipgit clone --depth 1 https://github.com/codecast-sh/codecastWrote 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/codecast-sh/codecast/cast-ship)<a href="https://agentmods.dev/skills/codecast-sh/codecast/cast-ship"><img src="https://agentmods.dev/badge/skills/codecast-sh/codecast/cast-ship/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/codecast-sh/codecast/cast-ship"><img src="https://agentmods.dev/badge/skills/codecast-sh/codecast/cast-ship.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.00081 | $0.00823 |
| Opus 5.5 | $0.00032 | $0.00329 |
| Sonnet 5.5 | $0.00016 | $0.00165 |
| Haiku 4.5 | $0.00008 | $0.00082 |
Grade A, and why
cast-ship 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 2d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Other tools poll a pull request. A shepherded pull request wakes this session when something happens to it, and the session sleeps in between.
Before committing
Run the checks the repository defines (typecheck, tests, lint) and fix what
they find. Read git status for changes that belong to other sessions and
leave those out. Group the rest into topical commits with short messages that
say what changed and why; never one commit for unrelated work.
Shipping everything in a shared checkout
When the work to ship is everything the sessions in a shared checkout left
uncommitted, not just this session's, use cast ship checkout rather than
committing by hand. cast ship checkout --dry-run --json freezes the tree and
groups the changed files by the session that wrote them, with each session's
state and last words. Judge every group before it goes: hold one whose session
is mid-change or says it is not finished, split a group that holds two
changes, rewrite messages to say what changed. cast ship checkout --plan
then ships exactly the frozen tree. When it stops (a check failing in a
shipped file, a shipped file importing a held one, a conflict), fix the cause
and plan again. The repo's [ship] table in .codecast/workspace.toml says
whether it pushes the default branch or opens a pull request, and what
deploys.
Open the pull request
Description, in order: the goal in one sentence, what changed and why, how it
was verified (commands and results, screenshots via cast image), what the
reviewer should look at first, and the session link from cast link. Push
and open with cast pr create -t "<title>" -b - (it runs gh pr create;
--dry-run shows the description first). When the bound task has a change
guide from its handoff, the description ends with it as a walkthrough, so
don't retell the change file by file. If the work is bound to a task, comment
the PR url on it.
Shepherd it
cast pr shepherd on # the branch's PR; a ref or url for another
cast state --status dormant "Shepherding PR #<n>; wakes on review, checks and merge"
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.
- 2d ago Changed · +15 lines c4fe5b42d601
- 9d ago Changed · +3 lines ebee449e8220
- 1mo ago First seen · 52 lines · 81 tokens per session scan A e7c344321725
cast-ship is a skill published in the GitHub repository codecast-sh/codecast (40 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 823 once invoked, about $0.0003 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-15.
Other skills, from other repositories
commit
Group unstaged changes into atomic commits by concern, matching repository style. Use when asked to "commit", "create a commit", or "commit changes". Don't use for pushing or pull requests (/to-pr).
pn-github-vertical-slices
Break a plan or PRD into tracer-bullet vertical slices and create GitHub Issues via GitHub MCP (official github/github-mcp-server). Dependencies first (AFK/HITL). Use after pn-writing-plans or pn-create-prd when work must ship as Issues.
ship
Stage, commit, and push every current Git repository change in one operation. Use when the user says /ship, “ship it”, “commit and push everything”, “stage everything”, “push everything”, or otherwise explicitly authorizes committing all current worktree changes without splitting or reviewing them individually.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
commit-context
Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.
commit-history
List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.