Borrowing it
Nothing to install: this file belongs to PacificStudio/openase. 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/PacificStudio/openase/main/.codex/skills/land/SKILL.mdgit clone --depth 1 https://github.com/PacificStudio/openaseWrote 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/pacificstudio/openase/land)<a href="https://agentmods.dev/skills/pacificstudio/openase/land"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/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/pacificstudio/openase/land"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/land.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.01033 |
| Opus 5.5 | $0.00012 | $0.00413 |
| Sonnet 5.5 | $0.00006 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00103 |
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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Land
Goals
- Ensure the PR is conflict-free with
origin/main. - Keep the current OpenASE validation and CI green.
- Address human review feedback before merge.
- Squash-merge the PR once checks pass.
- Do not yield while the branch is mergeable and there is still concrete work to do.
Preconditions
ghCLI is authenticated.- You are on the PR branch with a clean working tree, or you are prepared to commit/push outstanding intended changes first.
Validation Gate
Use the repo's actual Go + Svelte checks instead of Symphony's Elixir flow.
- Go/backend changes or unclear scope:
PATH="$PWD/.tooling/go/bin:/home/yuzhong/.local/go1.26.1/bin:$PATH" go test ./..../scripts/ci/lint.sh
- Frontend changes under
web/or unclear scope:npm --prefix web installnpm --prefix web run checknpm --prefix web run build
- Cross-cutting changes or uncertainty:
- Run all of the above before the final merge attempt.
Steps
- Locate the PR for the current branch.
- If the working tree has uncommitted intended changes, use the
commitskill and then thepushskill before proceeding. - Check mergeability and conflicts against
origin/main. - If conflicts exist, use the
pullskill to fetch and mergeorigin/main, resolve conflicts, rerun the applicable validation gate, then use thepushskill to publish the updated branch. - Review outstanding feedback:
- Top-level PR comments
- Inline review comments
- Review summaries /
CHANGES_REQUESTED
- Before implementing review feedback, confirm it does not conflict with the task's intent. If you disagree, respond with concise rationale and only ask the user if product intent is genuinely ambiguous.
- Reply to review threads before or alongside the corresponding code change so the record is clear.
- Watch CI and review state until the PR is ready:
- Preferred:
python3 .codex/skills/land/land_watch.py - Fallback:
gh pr checks --watchplus explicit review comment inspection withgh api.
- Preferred:
- If checks fail, inspect the failing run, fix the issue, rerun the applicable validation gate locally, commit, push, and restart the watch loop.
- When all checks are green and outstanding feedback is resolved or answered, squash-merge using the PR title/body.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 121 lines · 30 tokens per session scan A 5f0481fbbe7e
land is a skill published in the GitHub repository PacificStudio/openase (269 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,033 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-30.
Other skills, from other repositories
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
meta-codereview-current-diff
Read the current uncommitted diff, run three independent reviewers (safety + tests-coverage + style) in parallel, then arbitrate a single BLOCK / BLOCKWITHOVERRIDE / PASSWITHNOTES verdict. Use before commit when you want a multi-perspective second-opinion instead of a single-reviewer agent loop.
git-diff
Capture the current git diff (staged, working-tree, or staged file list) as text. Direct shell call for workflows that need repository diffs without an LLM agent loop.