Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/darkroomengineering/cc-settingsnpx agentmods add skills/darkroomengineering/cc-settings/shipWrote 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/darkroomengineering/cc-settings/ship)<a href="https://agentmods.dev/skills/darkroomengineering/cc-settings/ship"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/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/darkroomengineering/cc-settings/ship"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 145 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00045 | $0.04114 |
| Opus 5.5 | $0.00018 | $0.01646 |
| Sonnet 5.5 | $0.00009 | $0.00823 |
| Haiku 4.5 | $0.00005 | $0.00411 |
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 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.
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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Pipeline
Standalone Codex
Skip Claude's !command interpolation below. Run git branch --show-current, git status --porcelain, and git log --oneline -5
explicitly. Create a new reviewer with spawn_agent, continue it while live
with send_message, trigger another turn once it is idle with followup_task,
wait with wait_agent, and stop its current turn with interrupt_agent only
when necessary. Never spawn codex-verifier and never run codex-run.ts from inside Codex.
Writers share the working tree unless the live host explicitly offers
isolation. Assign non-overlapping ownership and serialize any implementer and
test-writer fixes; only read-only reviewers may overlap. Codex implementers are
not promised Claude worktree isolation. Codex also skips TLDR and uses
git diff --name-only, direct import searches, and test-name searches to choose
affected tests.
You are in Maestro orchestration mode. Execute the shipping checklist in order.
Claude current state
- Branch: !
git branch --show-current 2>/dev/null || echo "unknown" - Working tree: !
git status --porcelain 2>/dev/null | head -20 - Recent commits: !
git log --oneline -5 2>/dev/null || echo "no commits"
Pipeline (All Steps Mandatory)
Step 0: Preflight
ssh-add -l
If no identities loaded: Unlock 1Password and retry — git signing will fail otherwise. Agent drops mid-flow are a recurring cause of failed pushes; catch it now, not after the commit.
Read and validate package.json before choosing commands. Invalid JSON or invalid
script declarations block the pipeline. Do not commit until all applicable gates
in Steps 1–4 (typecheck/build/test/lint) are green; record an absent build script
as N/A with its reason. Skipping ahead is where amend churn comes from — --amend
to fix a lint error you would have caught in 30 seconds invalidates signatures and CI runs.
Step 1: Type Check
bunx tsc --noEmit
If errors: fix them. Do not proceed until clean.
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 · +12 lines 984a76121c5b
- yesterday Changed · -21 lines a2f2931d99ea
- 2d ago Changed · +3 lines e0edf3b537f5
- 9d ago Changed · +21 lines bf52cad4124d
- 17d ago Changed 719c390abd67
- 29d ago Changed · +3 lines 81e0c67d2869
- 1mo ago Changed · -18 tokens per session 4d87edceea6f
- 1mo ago Changed · +12 lines e8b0fa3524e8
- 1mo ago Changed · -3 lines 85171ff2508b
- 1mo ago First seen · 238 lines · 63 tokens per session scan A 69f94e100e24
ship is a skill published in the GitHub repository darkroomengineering/cc-settings (51 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 4,114 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-08-30.
Other skills, from other repositories
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
aiox-devops
Activate Gage (devops) for GitHub Repository Manager & DevOps Specialist. Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository.
aiox-devops
GitHub Repository Manager & DevOps Specialist (Gage). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized...
hatch3r-release
Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.