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 FlorianBruniaux/claude-code-plugins --skill land-and-deploygit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-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/florianbruniaux/claude-code-plugins/land-and-deploy)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/land-and-deploy"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/land-and-deploy/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/florianbruniaux/claude-code-plugins/land-and-deploy"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/land-and-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 4 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 226 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00024 | $0.02862 |
| Opus 5.5 | $0.00010 | $0.01145 |
| Sonnet 5.5 | $0.00005 | $0.00572 |
| Haiku 4.5 | $0.00002 | $0.00286 |
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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf -o /dev/null -w "%{http_code}" "${PROD_URL}" 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Land and Deploy
Complete landing pipeline: merge the PR, wait for CI, verify the deployment, run a health check.
Picks up where /ship left off. /ship creates the PR. This command merges it and verifies production.
Non-interactive by default. The user said "land it", so land it. Stop only for the critical readiness gate and hard blockers.
Instructions
Step 1: Pre-flight
# Verify GitHub CLI is authenticated
gh auth status
# Detect PR from current branch (or use argument if provided)
gh pr view --json number,state,title,url,mergeStateStatus,mergeable,baseRefName,headRefName
Stop conditions:
- GitHub CLI not authenticated → "Run
gh auth loginfirst" - No PR exists → "No PR found for this branch. Run
/shipfirst." - PR already merged → "PR is already merged."
- PR is closed → "PR is closed. Reopen it first."
Step 2: CI Status Check
# Check current CI status
gh pr checks --json name,state,status,conclusion
# Check for merge conflicts
gh pr view --json mergeable -q .mergeable
Stop conditions:
- Required checks FAILING → show failing checks, stop
mergeableisCONFLICTING→ "PR has merge conflicts. Resolve them and push before landing."- Required checks PENDING → proceed to Step 3 (wait for CI)
- All checks passing → skip to Step 3.5 (readiness gate)
Step 3: Wait for CI (if pending)
# Watch CI checks with 15-minute timeout
gh pr checks --watch --fail-fast
- CI passes → continue to Step 3.5
- CI fails → stop, show failures
- Timeout (15 min) → "CI has been running for 15 minutes. Investigate manually."
Record CI wait duration for the deploy report.
Step 3.5: Pre-Merge Readiness Gate
This is the one critical confirmation before an irreversible merge. Collect all evidence, then get explicit approval.
Review staleness check
# How many commits since the last review in this branch?
git log --oneline $(git merge-base HEAD origin/main)..HEAD | wc -l
# What changed after any review was done?
git log --oneline -10
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 · 367 lines · 24 tokens per session scan A 7f74b3d3b2c8
land-and-deploy is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (42 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 2,862 once invoked, about $0.0001 per session on Opus 5.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-09-04.
Other skills, from other repositories
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
submit-hook
Submit a deployed Uniswap v4 hook to the public univ4-hooks registry - format the listing, open a PR (issue fallback) so it lists on the hook marketplace.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.