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 skills/ianphil/chamber/shipnpx skills add ianphil/chamber --skill shipgit clone --depth 1 https://github.com/ianphil/chamberWrote 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/ianphil/chamber/ship)<a href="https://agentmods.dev/skills/ianphil/chamber/ship"><img src="https://agentmods.dev/badge/skills/ianphil/chamber/ship.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.00082 | $0.02596 |
| Opus 5 | $0.00041 | $0.01298 |
| Sonnet 5 | $0.00016 | $0.00519 |
| Haiku 4.5 | $0.00008 | $0.00260 |
Grade A, and why
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 4d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Skill
Drive Chamber work from a feature branch to a clean, reviewable pull request. This skill replaces the older pr workflow name; use it for "ship", "ship it", "open a PR", "prepare this PR", "finalize", "land this branch", and related shipping requests.
The user is ianphil. The default base branch is master unless a caller supplies a stack parent branch. Commits must include the Chamber Co-authored-by trailer. Use gh for all GitHub operations. Never use MCP.
Modes
Interactive mode
Use interactive mode for one-off user requests when defaults were not already approved. In this mode, ask before applying version bumps, changelog entries, Uncle Bob review, and optional packaging smoke.
Autopilot mode
Use autopilot mode when:
- The
issue-slateskill invokes this skill with confirmed slate defaults. - The user explicitly says to run on autopilot, ship the slate, or use defaults.
- A roadmap already records the answers for versioning, changelog, closing issues, review, and smoke policy.
In autopilot mode, do not stop for repeated confirmation prompts. Apply these defaults automatically:
| Prompt area | Autopilot default |
|---|---|
| Change classification | Pick the conventional kind (KaC canonical: added/changed/deprecated/removed/fixed/security; Chamber extensions: breaking/perf/refactor/docs/tests/build/ci/chore/packaging) from the diff; the release skill computes the actual version bump later from accumulated ## [Unreleased] entries. |
| Changelog | Append a bullet under the matching ### Heading of ## [Unreleased] using scripts/append-changelog-entry.js. |
| Closing issue | Include all planned issue refs from the roadmap or branch commit messages. |
| Uncle Bob | Run for non-trivial, runtime, architecture, SDK, security, or broad behavior changes; skip for small docs, tests, and focused UI fixes. |
| Packaging sandbox | Do not run npm run make:sandbox; use npm run package only when packaging/startup paths need smoke coverage. |
| PR base | Use the supplied stack parent branch; otherwise use master. |
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.
- 4d ago First seen · 261 lines · 82 tokens per session scan A 145299fd0d7f
ship is a skill published in the GitHub repository ianphil/chamber (11 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 2,596 once invoked, about $0.0004 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
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
skill-reviewer
Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.
surprise-me
Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for…