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 agentmods add skills/laurigates/claude-plugins/deploy-handoffnpx skills add laurigates/claude-plugins --skill deploy-handoffgit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/deploy-handoff)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/deploy-handoff"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/deploy-handoff.svg" alt="Measured on agentmods" 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.00039 | $0.01792 |
| Opus 5 | $0.00019 | $0.00896 |
| Sonnet 5 | $0.00008 | $0.00358 |
| Haiku 4.5 | $0.00004 | $0.00179 |
Grade A, and why
deploy-handoff 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 2d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Handoff Command
Generate professional handoff messages for deployed resources and services with all necessary information for developer handoff.
When to Use This Skill
| Use this skill when... | Use deploy-release instead when... |
|---|---|
| Handing off an already-deployed service to another developer or client | Cutting a new release tag or driving release-please automation |
| Documenting deployment details (URLs, env vars, monitoring) on a ticket | Publishing a draft, pre-release, or manual GitHub release |
| Onboarding a new team member with access information for a running service | Setting up release-please-config.json / .release-please-manifest.json |
| Composing a client-facing deployment summary | Writing the Dockerfile (container-development) or Skaffold config (skaffold-orbstack) |
Context
- Git remotes: !
git remote -v - Branch: !
git branch --show-current - Last commit: !
git log --oneline --max-count=1 - README: !
find . -maxdepth 1 -name \'README.md\' - Docker: !
find . -maxdepth 1 \( -name "Dockerfile" -o -name "docker-compose*.yml" \) - CI/CD: !
find . -path '*/.github/workflows/*' -maxdepth 3 -name '*.yml' - Config files: !
find . -maxdepth 1 \( -name ".env.example" -o -name "*.config.*" \)
Parameters
$1(RESOURCE_NAME, optional): Name of the deployed resource/service$2(DEPLOYMENT_TYPE, optional): Type of deployment (web-app, api, database, infrastructure, etc.)
Execution
Execute this deployment handoff documentation workflow:
Step 1: Discover resource details
Gather deployment details from current repository context. Identify relevant documentation and configuration files. Extract repository information and branch details.
Step 2: Collect technical information
Collect:
- Service/resource name and purpose
- Deployment environment details
- Access URLs and endpoints
- Configuration and environment variables
- Dependencies and prerequisites
- Monitoring and logging information
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.
- 2d ago First seen · 219 lines · 39 tokens per session scan A 1249580be78d
deploy-handoff is a skill published in the GitHub repository laurigates/claude-plugins (58 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,792 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
healthcheck
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).
cli-usage
Complete reference for the systemprompt CLI - 8 domains, 64+ subcommands for managing AI infrastructure, services, agents, cloud deployments, and analytics.
aiq-deploy
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
aspire-dev
Orchestrates Aspire distributed applications using the Aspire CLI and MCP tools. USE FOR: aspire start/stop, aspire describe, aspire doctor, view logs/traces, add integrations, debug resources, AppHost management. Also trigger for DistributedApplication.CreateBuilder, AddProject, AddContainer, or Aspire resource…
cloud-architecture
Master cloud architecture with AWS, Azure, GCP, cloud-native patterns, migration strategies, and cost optimization.
scalability-patterns
Master scalability patterns with load balancing, caching, database scaling, microservices, and horizontal scaling strategies.