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.
curl -O https://raw.githubusercontent.com/kwanpham2195/symphony-go/main/.agents/skills/land/SKILL.mdgit clone --depth 1 https://github.com/kwanpham2195/symphony-goWrote 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/kwanpham2195/symphony-go/land)<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.
<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>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.00038 | $0.00487 |
| Opus 5.5 | $0.00015 | $0.00195 |
| Sonnet 5.5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
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 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.
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
ghCLI is authenticated.- You are on the PR branch with a clean working tree.
Steps
- Locate the PR for the current branch.
- Run the full gate locally before any push:
make check - If uncommitted changes exist, commit with the
commitskill and push with thepushskill. - Check mergeability and conflicts against main.
- If conflicts exist, use the
pullskill to mergeorigin/mainand resolve, thenpushskill to publish. - Watch checks until complete:
gh pr checks --watch - If checks fail, pull logs, fix, commit, push, and re-watch:
gh pr checks gh run view <run-id> --log-failed - 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
pullskill first. - Do not use
--force; only--force-with-leasewhen history was rewritten.
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 · 61 lines · 38 tokens per session scan A d6829906da86
land is a skill published in the GitHub repository kwanpham2195/symphony-go (10 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 487 once invoked, about $0.0002 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.
Other skills, from other repositories
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…
verify-and-ship
Choose proportionate validation, fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
release
Prepare, verify, publish, and finish a coordinated Cyrus CLI release. Use when a user asks to release Cyrus, publish cyrus-ai, run a CLI release, or perform the /release workflow.
land
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.