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 juan294/cc-rpi --skill deployment-safetygit clone --depth 1 https://github.com/juan294/cc-rpiWrote 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/juan294/cc-rpi/deployment-safety)<a href="https://agentmods.dev/skills/juan294/cc-rpi/deployment-safety"><img src="https://agentmods.dev/badge/skills/juan294/cc-rpi/deployment-safety/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/juan294/cc-rpi/deployment-safety"><img src="https://agentmods.dev/badge/skills/juan294/cc-rpi/deployment-safety.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.00035 | $0.01022 |
| Opus 5 | $0.00017 | $0.00511 |
| Sonnet 5 | $0.00007 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
deployment-safety 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 3d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Safety
Merging to Main
Read the actual deployment topology: main may be canonical source, production,
or both. A merge/push that deploys production requires explicit production
authorization. A request to clean up dependency PRs is not release authorization.
Keep working branches and worktrees local. Finish applicable tests, coverage, typechecks, lint, build and deployment preflight locally, resolve failures, and integrate completed work locally into the documented integration branch. Inspect workflow and deployment triggers before the single authorized push of that completed branch. Never create Vercel Preview deployments or publish working branches/PRs for experimentation. If an integration push would create a Preview, stop before pushing and use only a documented, non-destructive bypass. Production publication remains separately and explicitly authorized. Read-only inspection of existing runs and deployments is allowed.
Dependency Batching
Inspect existing dependency PRs read-only. Apply the relevant updates together on one local task-owned branch based on the documented integration branch:
git switch -c chore/dependency-updates <integration-branch>
# Apply reviewed updates and run the complete applicable local gate.
Integrate the verified result locally. Never merge dependency PRs one-by-one, push fixes to their branches, request remote rebases, or create a batch PR as a debugging loop. Closing/commenting on existing PRs needs authorization.
CI Cost Awareness
Run tests, coverage, typechecks, lint, build and deployment preflight locally
when applicable. Use && or explicit status aggregation so an early failing
check cannot be hidden by later success. Inspect all trigger types before the
single authorized integration push, including auxiliary workflows and report
publication. Existing logs and statuses can be inspected without triggering runs.
Framework Upgrades
A green build alone does not establish runtime compatibility. Exercise local runtime smoke tests, packaging and platform preflight, and inspect existing platform logs/configuration. Never create a Vercel Preview. Record any remaining platform-only uncertainty in the candidate's release review; do not claim local tests prove an unexercised hosted runtime works.
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.
- 3d ago Changed · -36 lines b0f6b826b7c2
- 9d ago First seen · 170 lines · 35 tokens per session scan A e39b3713c4d8
deployment-safety is a skill published in the GitHub repository juan294/cc-rpi (5 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 1,022 once invoked, about $0.0002 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-31.
Other skills, from other repositories
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
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…
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
release
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
autoship
Runs a changesets npm release through the version PR, CI publish, and registry verification. Use when asked to "release this package", "autoship", "merge Version Packages", or diagnose a release that did not publish. For feature PRs use pr-creator or pr-babysitter.