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.5 | $0.00019 | $0.00128 |
| Sonnet 5.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 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.
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.
- 1mo 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 17d ago), licensed MIT. It adds 48 tokens to every session and 320 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-09-03.
Other skills, from other repositories
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…
aws-step-functions
Build workflows with AWS Step Functions state machines using the JSONata query language. Covers Amazon States Language (ASL) structure, state types, variables, data transformation, error handling, AWS service integration, and migrating from the JSONPath to the JSONata query language.
hyperpod-version-checker
Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches…
aws-lambda
Design, build, deploy, test, and debug serverless applications with AWS Lambda. Triggers on phrases like: Lambda function, event source, serverless application, API Gateway, EventBridge, Step Functions, serverless API, event-driven architecture, Lambda trigger. For deploying non-serverless apps to AWS, use…
hyperpod-ssm
Remote command execution and file transfer on SageMaker HyperPod cluster nodes via AWS Systems Manager (SSM). This is the primary interface for accessing HyperPod nodes — direct SSH is not available. Use when any skill, workflow, or user request needs to execute commands on cluster nodes, upload files to nodes…
walkthrough
Use when an unavoidable human-only operation needs a repeatable guided procedure, such as dashboard consent, physical access, credential entry, or an irreversible cutover approval. Not for repository tutoring or setup the agent can perform with available tools and authority.