Borrowing it
Nothing to install: this file belongs to nikzlabs/shipit. 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/nikzlabs/shipit/main/.agents/skills/dogfooding-shipit/SKILL.mdgit clone --depth 1 https://github.com/nikzlabs/shipitWrote 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/nikzlabs/shipit/dogfooding-shipit)<a href="https://agentmods.dev/skills/nikzlabs/shipit/dogfooding-shipit"><img src="https://agentmods.dev/badge/skills/nikzlabs/shipit/dogfooding-shipit/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/nikzlabs/shipit/dogfooding-shipit"><img src="https://agentmods.dev/badge/skills/nikzlabs/shipit/dogfooding-shipit.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.03349 |
| Opus 5.5 | $0.00032 | $0.01340 |
| Sonnet 5.5 | $0.00016 | $0.00670 |
| Haiku 4.5 | $0.00008 | $0.00335 |
Grade C, and why
dogfooding-shipit scanned grade C with 2 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
shipit service stop onboarding && rm -rf .inner-shipit/onboarding && shipit service start onboarding Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Leave it running when you are done — never `shipit service stop dev`.** Stopping it by hand buys nothing: archiving the session stops the service anyway. And the user often opens the inner UI after you report, so a sto How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dogfooding ShipIt in ShipIt
Opening the ShipIt repo in production ShipIt surfaces the dev Compose service as a manual preview — a whole second orchestrator, plus a Dockerfile.dogfood build, so it starts on demand rather than every boot. It shares the agent container's /workspace/node_modules (populated by agent.install at session boot) and runs Vite's dev server on the exposed port 3000, proxying /api, /ws, and /preview to the inner orchestrator on internal port 4000. It does not run its own npm install or a production vite build — the Compose file explains why that would be redundant and unsafe.
Start it with shipit service start dev. A first start may take minutes; a start that times out is still running — re-check with shipit service list. Start it whenever your change can be seen in the inner UI, and in it run the path the user takes, in the state the user is in (CLAUDE.md → Debugging the UI). A few minutes of start time buys a check unit tests cannot make, so "that needs the dogfood instance" is never a reason to ship a UI change unverified, to hand the decision back to the user, or to hand the user a check you can run on the machine you were given. If the container is paused, start fails with cannot start a paused container, try unpause instead; shipit service restart dev recovers it.
Leave it running when you are done — never shipit service stop dev. Stopping it by hand buys nothing: archiving the session stops the service anyway. And the user often opens the inner UI after you report, so a stopped service only makes them wait through another start. Say that it is running and point at it with a [the inner UI](shipit-preview://dev) chat link — the url from shipit service list is the container IP, which is yours to curl and not an address their browser can reach.
Local mode is a real exception to "ShipIt always runs in Docker"
The inner orchestrator runs with RUNTIME_MODE=local, which skips Docker entirely: no inner containers, no inner Compose, and inner agents spawn in-process via claude-adapter / codex-adapter rather than in a session worker container.
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.
- today Changed 44fe13be1c07
- 1mo ago Changed a74f2b4401e5
- 1mo ago Changed d521bdaa63b1
- 1mo ago Changed · +14 lines 89360eb8f0c9
- 1mo ago Changed c2b88fd8a42e
- 1mo ago Changed · +2 lines 3331bca877fb
- 1mo ago First seen · 123 lines · 81 tokens per session scan C 7d0255783721
dogfooding-shipit is a skill published in the GitHub repository nikzlabs/shipit (9 stars, last pushed today), licensed Apache-2.0. It adds 81 tokens to every session and 3,349 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
moai-ref-secops
DevSecOps, container, and API operational defensive security reference: CI/CD pipeline hardening, secret scanning, IaC misconfiguration detection, SAST/DAST integration, container image scanning, Kubernetes RBAC hardening, container-escape defense, runtime threat detection, OWASP API Top 10 operational defense, WAF…
kelos
Install and configure Kelos; author, document, inspect, troubleshoot, and operate its Kubernetes custom resources and CRD schemas in the kelos.dev API group using manifests, kubectl, or the kelos CLI. Use when a request names Kelos or a distinctive Kelos kind such as AgentConfig or TaskSpawner and concerns an…
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations. Not for: a loom orchestration job or CI pipeline job — see loom-ci-cd.
loom-docker
Docker and container expertise.
loom-kustomize
Kubernetes-native configuration management with Kustomize.
google-tag-manager
Skill "google-tag-manager" from VKirill/claude-lane-stack, covering 🎯 version requirements (june 2026), usage, use this skill when, do not use this skill when and purpose.