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 jeremylongworth-source/AgentSkills --skill deployment-plangit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/deployment-plan)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/deployment-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/deployment-plan/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/jeremylongworth-source/agentskills/deployment-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/deployment-plan.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.00048 | $0.00320 |
| Opus 5 | $0.00024 | $0.00160 |
| Sonnet 5 | $0.00010 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
deployment-plan 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 8d 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.
What it actually says
Deployment Plan
Core Workflow
- Identify artifact, target environment, hosting model, dependencies, release owner, users affected, and approval requirements.
- Document pre-deploy checks: build, tests, migrations, config, secrets, capacity, observability, and support readiness.
- Define deployment steps, rollout order, smoke tests, monitoring, and communication points.
- Include rollback or fallback triggers before deployment begins.
- Separate dry-run, staging, canary, and production steps.
- Record owners, timing, risks, and go/no-go criteria.
Safety Rules
- Do not deploy, change production config, run migrations, or restart services without explicit approval.
- Do not claim a deployment is safe without validation evidence.
- Escalate deployments involving customer data, auth, billing, migrations, high traffic, regulated workloads, or broad availability.
Deliverable Shape
For deployment plans, provide:
- Target artifact and environment
- Preconditions
- Deployment steps
- Smoke tests and monitoring
- Rollout and communication plan
- Rollback triggers
- Owners and approvals
- Go/no-go criteria
References
- Read
references/deployment-plan-checklist.mdwhen preparing deployment plans or runbooks.
What ships with it
2 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.
- 8d ago First seen · 46 lines · 48 tokens per session scan A cc7b109073b7
deployment-plan is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 9d ago), licensed MIT. It adds 48 tokens to every session and 320 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-09-03.
Other skills, from other repositories
aiq-deploy
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
dynamo-recipe-runner
Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.
doca-hardware-safety
Use this skill whenever the agent is about to recommend or apply a change that touches DPU / NIC hardware state on a live system — mlxconfig firmware-parameter write, NIC firmware burn, BFB reflash, NIC ↔ DPU mode flip, SR-IOV or device-emulation slot enable, kernel boot-parameter change (IOMMU, hugepages, VFIO), PCIe…
doca-setup
Use this skill when the user is dealing with the DOCA environment around their workload — verifying an install is healthy, preparing the build env (pkg-config, headers, LDLIBRARYPATH, hugepages, devlink, representors), debugging env-class failures, deciding container-vs-bare-metal deployment shape, or reaching a DOCA…
doca-upgrade
Use this skill when the user is contemplating a DOCA upgrade or downgrade — moving a host to a newer DOCA release, refreshing the BlueField BFB, bumping the NGC DOCA container tag, or rolling back. The discipline is detect → report → ASK → only-then guided upgrade: detect what is installed, discover what newer release…