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 zhpeng24/devkit --skill deployment-operationsgit clone --depth 1 https://github.com/zhpeng24/devkitWrote 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/zhpeng24/devkit/deployment-operations)<a href="https://agentmods.dev/skills/zhpeng24/devkit/deployment-operations"><img src="https://agentmods.dev/badge/skills/zhpeng24/devkit/deployment-operations/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/zhpeng24/devkit/deployment-operations"><img src="https://agentmods.dev/badge/skills/zhpeng24/devkit/deployment-operations.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.00057 | $0.00964 |
| Opus 5.5 | $0.00023 | $0.00386 |
| Sonnet 5.5 | $0.00011 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
deployment-operations 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 1mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Operations
Operate from observed state and an explicit target contract. Prefer the smallest reversible change that restores or advances the requested outcome.
Resolve the operating contract
- Read repository instructions, deployment docs, manifests, environment
examples, and the optional
.devkit/project.json. - Resolve the target environment, host or cluster, working directory, branch or artifact, runtime manager, health probes, and rollback unit.
- Treat project-profile values as defaults, not authorization. Never infer permission for production mutation, data deletion, secret rotation, volume removal, migration rollback, or another irreversible action.
- If target identity is still ambiguous and the next command can affect live traffic or data, stop and ask for that target. Read-only discovery can proceed.
Use references/deployment-playbook.md for runtime-specific commands and project
profile mappings. Use references/incident-response.md for outages and degraded
service.
Route the request
| Mode | Required outcome |
|---|---|
| Plan | Produce a target-specific sequence, evidence gates, rollback point, and stop conditions. |
| Development runtime | Start or reconcile the project-approved local processes and dependencies. |
| Deploy | Deliver a known commit, image, or package and verify user-visible readiness. |
| Diagnose | Locate the failing layer from read-only evidence before changing state. |
| Rollback | Restore a known-good artifact or configuration and repeat the same probes. |
| Harden | Improve secrets, permissions, resource limits, observability, or runbooks without inventing live state. |
Operate
- Preflight. Inspect worktree state, artifact identity, target reachability, runtime configuration, dependencies, capacity, and current health. Validate Compose, systemd, or Kubernetes configuration before applying it.
- Declare evidence. Name the exact success probes and the rollback boundary. A process being alive is not readiness; include dependency and user-path probes when the goal depends on them.
- Change one coherent unit. Update only the requested services or resources. Prefer rolling/recreate operations over teardown. Do not use volume deletion, force pushes, hard resets, or unreviewed migration reversal as shortcuts.
- Verify. Re-run the failed or target probe, then one upstream and one downstream check when applicable. Confirm the deployed commit, image digest, package version, or configuration revision.
- Record. Report target, artifact, commands, concise results, data or secrets touched, rollback status, and remaining risk. Update the project runbook when ports, environment variables, runtime contracts, or operator actions changed.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 89 lines · 57 tokens per session scan A be59c9313a4f
deployment-operations is a skill published in the GitHub repository zhpeng24/devkit (2 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 964 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-31.
Other skills, from other repositories
deploy-akashic
A deployment procedure for an Akashic project that checks and merges an approved pull request, then submits the resulting code revision to update a Docker-based service. The host system handles stopping, moving, and restarting the service.
release
Used to release all toolbox, integrations, agents. Use when releasing a subproject to PyPI, Docker Hub, or when the user asks to release or publish.
ferrogate-release
Use when cutting a FerroGate release — building the container image and publishing it to GHCR. Covers the standing directive to NOT use GitHub Actions (too slow) and instead gate on the local ferrogate-test suite then push locally, including the no-sudo/no-Docker host path (musl-static + crane). Use for "release"…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…