symphony-go: Skill for Claude Code

.agents/skills/land/SKILL.md

land is a skill for Claude Code, Codex from kwanpham2195/symphony-go. It costs 38 tokens per session (487 once invoked), scanned A, original, MIT.

A workflow for completing a GitHub pull request by resolving conflicts, waiting for automated checks, handling review comments, and squash-merging it when ready.

In plain words
What is it for?
Use it when a pull request should be taken through to merge. It checks the branch, updates conflicts, watches CI, addresses failures, and squash-merges after checks pass.
Why use it?
It coordinates the final review and integration work, reducing the chance of merging code with conflicts, failing checks, or unanswered comments.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is kwanpham2195/symphony-go's own configuration. It tells Claude Code and Codex how to work on symphony-go itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything symphony-go configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kwanpham2195/symphony-go. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kwanpham2195/symphony-go/main/.agents/skills/land/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/kwanpham2195/symphony-go

Made for: Claude Code, Codex.

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.

agentmods badge for land

README.md
[![agentmods](https://agentmods.dev/badge/skills/kwanpham2195/symphony-go/land/github.svg)](https://agentmods.dev/skills/kwanpham2195/symphony-go/land)
Your own site
<a href="https://agentmods.dev/skills/kwanpham2195/symphony-go/land"><img src="https://agentmods.dev/badge/skills/kwanpham2195/symphony-go/land/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.

agentmods 80×15 button for land

Your own site · 80×15
<a href="https://agentmods.dev/skills/kwanpham2195/symphony-go/land"><img src="https://agentmods.dev/badge/skills/kwanpham2195/symphony-go/land.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 487 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.00487
Opus 5 $0.00019 $0.00244
Sonnet 5 $0.00008 $0.00097
Haiku 4.5 $0.00004 $0.00049

Measured 9d ago against content hash d6829906da86, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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

.agents/skills/land/SKILL.md · 61 lines

What it actually says

Land

Goals

  • Ensure the PR is conflict-free with main.
  • Keep CI green and fix failures when they occur.
  • Squash-merge the PR once checks pass.
  • Do not yield until the PR is merged; keep the loop running unless blocked.

Preconditions

  • gh CLI is authenticated.
  • You are on the PR branch with a clean working tree.

Steps

  1. Locate the PR for the current branch.
  2. Run the full gate locally before any push:
    make check
    
  3. If uncommitted changes exist, commit with the commit skill and push with the push skill.
  4. Check mergeability and conflicts against main.
  5. If conflicts exist, use the pull skill to merge origin/main and resolve, then push skill to publish.
  6. Watch checks until complete:
    gh pr checks --watch
    
  7. If checks fail, pull logs, fix, commit, push, and re-watch:
    gh pr checks
    gh run view <run-id> --log-failed
    
  8. When all checks are green, squash-merge:
    pr_title=$(gh pr view --json title -q .title)
    pr_body=$(gh pr view --json body -q .body)
    gh pr merge --squash --subject "$pr_title" --body "$pr_body"
    

Review Handling

  • Address all review comments before merging (code fix or explicit pushback with rationale).
  • For each comment: accept, clarify, or push back. State the mode before changing code.
  • Reply before pushing code changes.

Failure Handling

  • If checks fail, inspect with gh run view --log-failed, fix locally, commit, push, re-watch.
  • Use judgment on flaky failures (timeouts on one platform) — may proceed.
  • If push is rejected, use the pull skill first.
  • Do not use --force; only --force-with-lease when history was rewritten.
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.

  1. 9d ago First seen · 61 lines · 38 tokens per session scan A d6829906da86

Subscribe to this mod's changes

land is a skill published in the GitHub repository kwanpham2195/symphony-go (10 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 487 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-08-31.

Related

Other skills, from other repositories

taiyi-integration

A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.

Dong90/oh-my-taiyiforge · 27 tokens

release-core-test

Invoke when dev-testing a Cyrus change that spans CYPACK (edgeworker + CLI) and CYHOST (Vercel-hosted GUI) and the hosted GUI needs to point at an unreleased cyrus-core from this repo. Publishes cyrus-core (and claude-runner if needed) as a -test.N prerelease under the npm test dist-tag so CYHOST can install it via…

cyrusagents/cyrus · 114 tokens

release

CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.

oliver-kriska/claude-elixir-phoenix · 60 tokens

commit-pr

Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…

ZaxbyHub/opencode-swarm · 100 tokens

git-workflow

Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.

ownpilot/OwnPilot · 42 tokens

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.

stevesolun/ctx · 67 tokens