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 agentmods add commands/grainulation/wheat/nextgit clone --depth 1 https://github.com/grainulation/wheatWhat 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 | $0.00000 | $0.00322 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 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 yesterday.
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.
- yesterday 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 4mo 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
advisor
Advisory gate for triage or plan decisions. Spawns a second-opinion agent that challenges assumptions, surfaces risks, and proposes alternatives before the decision commits. Based on Anthropic advisor tool pattern.
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.
pm-review
Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.
new
Creates a new item in a module that supports the new capability.
card
Open one self-contained OverClick card.
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.