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 KyaniteLabs/checkyourself --skill 11-hosting-deployment-releasegit clone --depth 1 https://github.com/KyaniteLabs/checkyourselfWrote 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/kyanitelabs/checkyourself/11-hosting-deployment-release)<a href="https://agentmods.dev/skills/kyanitelabs/checkyourself/11-hosting-deployment-release"><img src="https://agentmods.dev/badge/skills/kyanitelabs/checkyourself/11-hosting-deployment-release/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/kyanitelabs/checkyourself/11-hosting-deployment-release"><img src="https://agentmods.dev/badge/skills/kyanitelabs/checkyourself/11-hosting-deployment-release.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.01672 |
| Opus 5 | $0.00028 | $0.00836 |
| Sonnet 5 | $0.00011 | $0.00334 |
| Haiku 4.5 | $0.00006 | $0.00167 |
Grade A, and why
hosting-deployment-release 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 9d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hosting-deployment-release
Choose hosting and deployment patterns, design safe releases, configure health checks, and plan rollbacks.
Operating contract
Act as a production hardening specialist for 11 Hosting & Deployment. Use model-agnostic reasoning: no instruction, output, or workflow in this capability depends on a particular model vendor or agent runtime. Prefer deterministic evidence over persuasive prose. When evidence is missing, name the assumption and make it visible in the output.
When to activate
Use this capability for hosting decisions, platform selection, container deployment, serverless deployment, domains, DNS, TLS, staging/production environments, blue-green, canary, rolling deploys, migrations during deploy, health checks, smoke tests, and rollback plans.
Inputs to request or inspect
- application architecture
- runtime requirements
- traffic profile
- deployment scripts
- environment config
- migration plan
Work protocol
- Choose hosting based on operational complexity, latency, scaling, data locality, team skills, cost, compliance, and rollback needs.
- Separate build, release, and run stages so artifacts can be promoted and rolled back safely.
- Design deploys around health checks, readiness, liveness, drain behavior, migrations, and dependent service availability.
- Use progressive delivery for risky changes: canary, blue-green, feature flags, staged traffic, and automatic rollback signals.
- Define smoke tests that prove the deployed artifact, configuration, database compatibility, and critical external integrations.
- Document rollback versus roll-forward decisions before launch.
Required output format
Return a concise report with these sections unless the user requested a concrete file or code diff:
- Scope interpreted — what is in and out.
- Findings / decisions — ordered by production risk, not by discovery order.
- Recommended actions — owner-ready tasks with priority and rationale.
- Verification evidence — tests, scans, contracts, telemetry, commands, or review steps required.
- Residual risk / assumptions — what remains uncertain and how to resolve it.
- Hand-offs — other capabilities that should review the work.
What ships with it
1 file 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.
- 9d ago First seen · 126 lines · 57 tokens per session scan A 1b2abc6f81a9
hosting-deployment-release is a skill published in the GitHub repository KyaniteLabs/checkyourself (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,672 once invoked, about $0.0003 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
docker-deploy
Use this skill when building, containerizing, or deploying WrongStack with Docker. Triggers: user says "docker", "container", "dockerfile", "image", "docker-compose", "deploy", "containerize", "registry", "multi-stage", "distroless".
kubernetes-specialist
Use when managing Kubernetes clusters, debugging Pods and workloads, designing Helm charts, reviewing manifests, or improving deployment, scaling, and observability practices.
terraform
Terraform and OpenTofu configuration, modules, testing, state management, and HCL review. Use when working with Terraform, OpenTofu, HCL, tfvars, tftest, state migration, or IaC patterns.
kubernetes
Diagnose and fix Kubernetes pods, services, networking, storage, and rollout failures with kubectl. Safety-first, read-only by default.
container-orchestration
Docker, Kubernetes, and AWS ECS/Fargate patterns. Triggers on: Dockerfile, docker-compose, kubernetes, k8s, helm, pod, deployment, service, ingress, container, image, ecs, fargate, task definition, ecs service, awsvpc, FARGATESPOT, ALB, ecs vs kubernetes.
proxmox-cluster-ops
Operate a Proxmox VE cluster safely — read-only inspection with pvesh/pct/qm/pvecm instead of hand-editing a live guest, node-by-node package updates that respect quorum, and the shape of joining a new node to an existing cluster. Use when inspecting cluster or guest state, planning a rolling update across cluster…