Borrowing it
Nothing to install: this file belongs to AgentSystemLabs/nebula. 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/AgentSystemLabs/nebula/main/.claude/skills/land/SKILL.mdgit clone --depth 1 https://github.com/AgentSystemLabs/nebulaWrote 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/agentsystemlabs/nebula/land)<a href="https://agentmods.dev/skills/agentsystemlabs/nebula/land"><img src="https://agentmods.dev/badge/skills/agentsystemlabs/nebula/land.svg" alt="Measured on agentmods" 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.00133 | $0.01658 |
| Opus 5 | $0.00067 | $0.00829 |
| Sonnet 5 | $0.00027 | $0.00332 |
| Haiku 4.5 | $0.00013 | $0.00166 |
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 today.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A landing chore is seven commands. On 2026-09-04 a three-word "commit push and merge" took 17 minutes because the SELF-IMPROVING LOOP ran around it, and the user asked why. This skill is the refinement: no PROMPT DADDY rewrite, no MEMORY LOG entry unless something new bit you, no PROJECT TERMS pass. The reply is OUTPUT DOCTOR's short form — OVERVIEW and NEXT STEPS.
1. Read the situation — three commands, then decide the shape
git status --short && git branch --show-current && git rev-list --left-right --count HEAD...origin/main
gh pr view --json number,state,url,mergeStateStatus,headRefName 2>/dev/null # a PR on this branch?
git diff --stat origin/main -- <the dirty paths> # is every hunk yours?
- Dirty SHARED CHECKOUT on
main("commit push and merge") → shape A: branch, commit, push, PR, merge, fast-forward back. Only the paths the task touched —git add <paths>, never-A: other sessions' hunks are in this tree too (.claude/MEMORY.md,TERMS.md,gotchas.mdare usually theirs as well as yours; take the file if your lines are in it, they ride along). - A branch with an open PR (a PR SESSION, "fix conflicts … babysit … merge") → shape B: bring
origin/mainin, answer the comments, wait for the check, merge. - "make pr" → shape A up to the pull request, then stop. When the third command's right-hand
count is above zero and the moved paths overlap yours (
git diff --stat HEAD...origin/main), mergeorigin/mainfirst (§5) so the PR opens CLEAN, not CONFLICTING (2026-09-05: one commit into the same three memory files).
2. The gate — before anything leaves the machine
make ci (or make memory-check recall-eval terms-check when no crate changed), logged to the
scratchpad — the GUARD HOOK blocks cargo … | tail. Red and not yours (git stash is blocked; prove it
with git diff origin/main -- <file>) → say so and stop; do not push over a red gate.
3. Commit and push
git switch -c <kebab-branch> # from main; a worktree branch is already on one
git add <explicit paths>
git commit -F <scratchpad>/msg # never -m: backticks in "…" are command-substituted
git push -u origin <branch>
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.
- today First seen · 95 lines · 133 tokens per session scan A ebd4fcb3d517
land is a skill published in the GitHub repository AgentSystemLabs/nebula (106 stars, last pushed today), licensed MIT. It adds 133 tokens to every session and 1,658 once invoked, about $0.0007 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-09-06.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…