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/code-saurabh/openskills/land-and-deploynpx skills add CODE-SAURABH/OpenSkills --skill land-and-deploygit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWrote 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/code-saurabh/openskills/land-and-deploy)<a href="https://agentmods.dev/skills/code-saurabh/openskills/land-and-deploy"><img src="https://agentmods.dev/badge/skills/code-saurabh/openskills/land-and-deploy.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.00070 | $0.02238 |
| Opus 5 | $0.00035 | $0.01119 |
| Sonnet 5 | $0.00014 | $0.00448 |
| Haiku 4.5 | $0.00007 | $0.00224 |
Grade A, and why
land-and-deploy scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf https://your-app.com/health | jq . How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Land and Deploy
You are the release engineer who takes an approved PR from "approved" to "verified in production." This is the final mile. Everything before this was preparation. This is the moment where preparation meets reality — and reality has a way of finding surprises.
Go slow here. Every step has a verification. Never assume a step succeeded without checking.
Land and Deploy Principles
- Approved is not shipped. CI can pass and the deploy can still fail. The feature can deploy and still not reach users. Verify at every stage.
- One PR per deploy. Never stack deploys. Land one, verify it, then land the next.
- The rollback plan is not optional. Know how to undo this deploy before you start it.
- Speed kills here. The pressure to ship fast causes skipped verification steps. Skipped steps cause incidents. Take the five extra minutes.
- Silence after deploy is not success. Actively verify — do not assume it worked because nothing broke loudly.
Step 0: Pre-Land Checklist
Before touching the merge button:
- PR has explicit approval from a qualified reviewer
- All CI checks are green — not just the required ones
- No merge conflicts (re-check — new commits to main since approval can create conflicts)
- Deploy environment is ready (no ongoing incident, no freeze window, no other deploy in progress)
- Rollback plan confirmed: know the exact command to revert this deploy
- Feature flag confirmed (if applicable): deploy can happen before the flag is flipped
- On-call / relevant team notified if this is a high-risk change
- Database migrations reviewed: are they zero-downtime?
Step 1: Merge
Choosing the merge strategy
| Strategy | When to use | Effect on history |
|---|---|---|
| Squash merge | Feature branches with messy interim commits | One clean commit on main per PR |
| Merge commit | Long-lived branches, audit trail needed | Preserves full branch history |
| Rebase merge | Linear history required, clean commits on branch | Linear history, replays commits |
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.
- 5d ago First seen · 299 lines · 70 tokens per session scan A abffe117e353
land-and-deploy is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (2 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 2,238 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
aws-ci-cd-release-engineer
Review AWS CI/CD and release safety across CodePipeline, CodeBuild, CodeDeploy, GitHub Actions, GitLab, artifact provenance, deployment gates, approvals, tests, progressive delivery, rollback, change correlation, and incident-prevention recommendations. Use when AWS releases or pipelines can affect production…
merge-queue-thrash-stop-inflow-and-open-prs-as-drafts
When main moves faster than the slowest CI leg, every open branch goes stale before it can merge and the whole queue jams with nothing red. Use when: (1) several PRs sit at mergeStateStatus BEHIND with auto-merge armed and none of them lands; (2) branches are being updated, re-running CI and going stale again before…
claude-plugin-repo-ci-release
Wire up CI validation and automatic release-cutting for a Claude Code plugin or marketplace repo (a repo with a .claude-plugin/marketplace.json and plugins/). Adds two GitHub Actions — a structure validator that runs on every PR/push, and a release-on-version-bump job that cuts a GitHub Release whenever a VERSION file…
abd-devops
ABD DevOps agent: scaffolds CI/CD, validates .env.example coverage, checks Dockerfile hygiene, and handles release tasks.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.