A post-merge workflow skill for checking a merged code change, verifying continuous integration (automated build and test checks), optionally checking deployment, and cleaning up branches.

Use it after a pull request is merged to identify the merge, inspect CI results, watch running checks, review deployment status, and clean up branches.

It helps confirm that a merged change passed its checks and that the repository is ready for the next piece of work.

landed — Skill for Claude Code by stranma/claude-code-python-template

Install

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.

Any agent

npx skills add stranma/claude-code-python-template --skill landed

Clone the repo

git clone --depth 1 https://github.com/stranma/claude-code-python-template

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/stranma/claude-code-python-template/landed/github.svg)](https://agentmods.dev/skills/stranma/claude-code-python-template/landed)

Your own site

<a href="https://agentmods.dev/skills/stranma/claude-code-python-template/landed"><img src="https://agentmods.dev/badge/skills/stranma/claude-code-python-template/landed/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/stranma/claude-code-python-template/landed"><img src="https://agentmods.dev/badge/skills/stranma/claude-code-python-template/landed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,126 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00026	$0.01126
Opus 5.5	$0.00010	$0.00450
Sonnet 5.5	$0.00005	$0.00225
Haiku 4.5	$0.00003	$0.00113

Measured 1mo ago against content hash 4e7a39758495, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

landed 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.

.claude/skills/landed/SKILL.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Landed

Post-merge lifecycle command. Run this after a PR is merged to verify CI, check deployments, clean up branches, and identify next steps.

Step 1: Detect Merged PR

Identify the PR that was just merged.

Run git branch --show-current to get the current branch
If already on master:
- Check git reflog --oneline -20 for the previous branch name
- If no branch found, ask the user for the PR number or branch name

Look up the merged PR:

gh pr list --state merged --head <branch> --json number,title,mergeCommit -L 1

If no PR found: ask the user for the PR number directly
Display: PR number, title, merge commit SHA

Pre-check: Run gh auth status early. If not authenticated, stop and instruct the user to run gh auth login.

Step 2: Verify Merge CI

Check that CI passed on the merge commit.

List recent runs on master:

gh run list --branch master -L 20 --json status,conclusion,databaseId,name,headSha

Filter to runs whose headSha matches the merge commit SHA
Evaluate all matched runs:
- in_progress: watch still-running run(s) with gh run watch <id>
- success: all matched runs must be completed with conclusion=success to proceed
- failure: show details via gh run view <id> --log-failed for each failing run
  - Ask: "Is this a recurring issue or specific to this PR?"
  - If recurring: suggest adding to /done validation or pre-merge CI
  - If specific: diagnose inline from the failed log output

Step 3: Deployment Verification (Configurable)

Check for deployment status if configured.

Check if .claude/deploy.json exists
If it exists:
- Read the file and iterate over configured environments
- For each environment:
  - Watch the deployment workflow: gh run list --workflow <workflow> --commit <merge-commit-sha> --json status,conclusion,databaseId
  - If health_check URL is configured, fetch it and verify a 200 response
- Report per-environment status (success/failure/in_progress)
If no config file:
- Ask the user: "Is there a deployment to verify? (skip if none)"
- If user says no or skips: mark as "skipped"

Read the full file on GitHub · 117 lines

Changes

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 · 117 lines · 26 tokens per session scan A 4e7a39758495

Subscribe to this mod's changes

landed is a skill published in the GitHub repository stranma/claude-code-python-template (2 stars, last pushed 6mo ago), licensed MIT. It adds 26 tokens to every session and 1,126 once invoked, about $0.0001 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-08-31.

Claude Code DevOps and cloud Git and workflow Releases claude monorepo project-template

landed

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Landed

Step 1: Detect Merged PR

Step 2: Verify Merge CI

Step 3: Deployment Verification (Configurable)

What this file has done since we first saw it

Other skills, from other repositories

releasing-weaverse-sdks

npm

dev-workflow

cargo-release

deliver

oma-scm