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.
git clone --depth 1 https://github.com/gmickel/flow-nextWrote 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/commands/gmickel/flow-next/land)<a href="https://agentmods.dev/commands/gmickel/flow-next/land"><img src="https://agentmods.dev/badge/commands/gmickel/flow-next/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/commands/gmickel/flow-next/land"><img src="https://agentmods.dev/badge/commands/gmickel/flow-next/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.00013 | $0.00130 |
| Opus 5.5 | $0.00005 | $0.00052 |
| Sonnet 5.5 | $0.00003 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
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 22d 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
IMPORTANT: This command MUST invoke the skill flow-next-land
The ONLY purpose of this command is to call the flow-next-land skill. You MUST use that skill now.
Arguments: $ARGUMENTS
Pass the named pull request and current session authorization to the skill. It resolves feedback and CI, checks the specs at the PR head, and merges when ready and authorized. It prints one terminal LAND_VERDICT line.
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.
- 22d ago Changed · +1 lines 78e87e5512d4
- 27d ago Changed · +2 lines · -12 tokens per session f1f93f8e18dd
- 1mo ago Changed e2488af51e17
- 1mo ago First seen · 14 lines · 25 tokens per session scan A affc44b4d363
land is a command published in the GitHub repository gmickel/flow-next (711 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 130 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-09-03.
Other commands, from other repositories
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
gsd:ship
Create PR, run review, and prepare for merge after verification passes.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
jira-release
../../plugins/jira-orchestrator/commands/release.md.