Borrowing it
Nothing to install: this file belongs to joosure/Maestro. 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/joosure/Maestro/main/.codex/skills/land/SKILL.mdgit clone --depth 1 https://github.com/joosure/MaestroWrote 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/joosure/maestro/land)<a href="https://agentmods.dev/skills/joosure/maestro/land"><img src="https://agentmods.dev/badge/skills/joosure/maestro/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.00038 | $0.02411 |
| Opus 5 | $0.00019 | $0.01205 |
| Sonnet 5 | $0.00008 | $0.00482 |
| Haiku 4.5 | $0.00004 | $0.00241 |
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 7d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 7d ago First seen · 226 lines · 38 tokens per session scan A 160451476b1b
land is a skill published in the GitHub repository joosure/Maestro (46 stars, last pushed 1mo ago), licensed AGPL-3.0. It adds 38 tokens to every session and 2,411 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-30.
Other skills, from other repositories
npm-publish
Use when publishing this package to npm — a version release (npm publish), verifying the registry/pi.dev listing, or diagnosing npm auth failures (E403 2FA/token errors). Token-based flow via NPMTOKEN in .env.local with a temp userconfig, the leakage gate before every publish, post-publish verification and…
owndiff-pre-commit
Audit OwnDiff changes before committing or releasing by checking scope, generated artifacts, private data, documentation accuracy, version consistency, structured files, tests, and the OwnDiff ownership gate. Use when a user asks to verify, clean up, prepare, commit, publish, or release changes in the OwnDiff…
release
Generate or update changelog and release notes from project history.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
release-jetbrains
Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.
release
Prepare a named version: preflight, version consistency, build/package, smoke test, checksums/notes, and release readiness. Publishing/tagging/deploy need separate authorization. Explicit-only.