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 infohata/mind-vault --skill landgit clone --depth 1 https://github.com/infohata/mind-vaultWrote 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/infohata/mind-vault/land)<a href="https://agentmods.dev/skills/infohata/mind-vault/land"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/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.00000 | $0.02570 |
| Opus 5 | $0.00000 | $0.01285 |
| Sonnet 5 | $0.00000 | $0.00514 |
| Haiku 4.5 | $0.00000 | $0.00257 |
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 8d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
land
The operational close of the sprint workflow — the step that ships a review-cleared, docs-finalized PR and reclaims its disposable infrastructure. Everything destructive or irreversible about concluding an IDEA lives here, separated from /wrap (which is non-destructive documentation finalization).
Canonical chain: /idea → /plan → /work → /wrap (docs) → /review-loop → /land (merge) → /compound. /land is the named merge stage — what used to hide behind /wrap --scope=full. The single /review-loop runs over the wrapped (docs-finalized) PR, then /land merges and tears down.
Two operations, three modes. The merge is pre-merge (it performs the squash-merge); teardown is post-merge (destructive, requires the PR to have landed). /land mode-detects which applies:
/land NNNpre-merge (PR open) — atomic merge on a non-protected target, then (since the merge unblocks teardown) teardown in the same pass. Protected target → no merge, hand back the PR URL./land NNNpost-merge (PR already merged) — teardown only. The merge already happened (human-clicked, or a prior/landon a protected target); this reclaims the worktree./land --integration <batch-iso>— sprint-auto v3.2 batch teardown (no merge, no docs): tear down the integration worktree + branch + every per-IDEAauto/<slug>worktree/branch.
When to use
TRIGGER when:
- A PR has cleared
/review-loopat its docs-finalized (post-/wrap) state and is ready to merge —/land NNN. - A PR merged (human-clicked or protected-target) and a parallel worktree/stack still needs teardown —
/land NNNpost-merge. - A sprint-auto v3.2 batch's
[INTEGRATION]PR has merged and the batch worktrees need reclaiming —/land --integration sprint-auto-<batch-iso>. - Phrasings: "merge it", "land the PR", "ship the IDEA", "tear down the worktree", "clean up the sprint stack".
SKIP when:
- Docs aren't finalized yet — run
/wrap NNNfirst (the precondition guard will refuse anyway). - The review loop hasn't cleared — merging unreviewed code is never
/land's job. - The target branch is protected AND you only want docs — that's
/wrap, not/land.
What ships with it
2 files 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.
- 8d ago First seen · 104 lines · 0 tokens per session scan A 862533e192e6
land is a skill published in the GitHub repository infohata/mind-vault (2 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,570 tokens. 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-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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.