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/grainulation/wheatWrote 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/grainulation/wheat/next)<a href="https://agentmods.dev/commands/grainulation/wheat/next"><img src="https://agentmods.dev/badge/commands/grainulation/wheat/next/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/grainulation/wheat/next"><img src="https://agentmods.dev/badge/commands/grainulation/wheat/next.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.00000 | $0.00322 |
| Opus 5.5 | $0.00000 | $0.00129 |
| Sonnet 5.5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
next 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.
What it actually says
/next -- Route next steps through Farmer
You just finished a slash command or a batch of work. The user monitors via Farmer on their phone and cannot see CLI text output.
Use AskUserQuestion to present what just happened and what comes next. This is the ONLY way the user sees results.
Process
-
Summarize what was just produced in the question text (1-2 sentences -- claim counts, key findings, what changed)
-
Pick 2-4 next steps based on sprint state. Use this decision tree:
- Unresolved conflicts exist -> suggest
/resolve - Claim has no corroboration -> suggest
/witness <id> <url> - Topic has weak evidence -> suggest
/research <topic>or/prototype - Sprint is late-phase with gaps -> suggest
/blind-spot - Sprint ready for output -> suggest
/brief,/present, or/handoff - Multiple sprints exist -> suggest
/merge
- Unresolved conflicts exist -> suggest
-
Call AskUserQuestion with the summary as the question and next steps as options. Keep option labels short (3-5 words), put detail in descriptions.
-
Act on the user's choice -- run whatever they picked.
Rules
- Header should be contextual (e.g., "After /brief", "After research")
- Don't include a "do nothing" option unless the user might genuinely want to stop
- If agents just completed, mention how many and what they did
- multiSelect: false unless the options are independent parallel tasks
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 · 30 lines · 0 tokens per session scan A 9155165ecd3e
next is a command published in the GitHub repository grainulation/wheat (20 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 322 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-30.
Other commands, from other repositories
mcptoon-setup
Set up or repair the mcptoon CLI for this machine (install, verify, diagnose).
safe-build
Build the application for development or production.
local
Command "local" from getsentry/toolkit, covering examples, start the server and tail events (default), run your app with the local server auto-enabled, use a custom port and only show errors and logs (filter out transactions).
auth
Command "auth" from getsentry/toolkit, covering examples, oauth login (recommended), token login, read-only oauth login and custom oauth scopes.
debug-files
Command "debug-files" from getsentry/toolkit, covering examples, inspect a debug information file (auto-detects the format), bundle jvm sources with a debug id, exclude additional directories and output as json.
feedback
Modern User Feedback is stored as Feedback issues. The command always limits issue searches to issue.category:feedback; it does not use the legacy User Reports API.