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/grainulatorWrote 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/grainulator/next)<a href="https://agentmods.dev/commands/grainulation/grainulator/next"><img src="https://agentmods.dev/badge/commands/grainulation/grainulator/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/grainulator/next"><img src="https://agentmods.dev/badge/commands/grainulation/grainulator/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.00262 |
| Opus 5 | $0.00000 | $0.00131 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
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 today.
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 — Show next actions
Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir <sprint> or grainulator.compile. Use the resulting next_actions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful Auto work already authorized by the active task.
Next-step output
After a meaningful pass, use the current compiler's next_actions to present exactly two bullet lists labeled Auto and Manual. Auto is work the agent can continue under existing authorization. Manual is only work requiring the user's decision, access, or action. Classify using the current request and constraints; compiler suggestions never grant permission. Continue authorized Auto work without asking again.
Keep 2–3 useful actions total when available, use short concrete labels and commands where useful, and show None. for an empty group. Do not invent work to fill a quota. Never omit next steps merely because compilation is ready or the answer should be brief. Refresh stale compilation first and exclude work the user removed from scope. When the user asks only for next steps, output only these two lists: no findings recap, counts, reasons, or offer to continue.
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.
- today First seen · 10 lines · 0 tokens per session scan A 4e5e3f3803bd
next is a command published in the GitHub repository grainulation/grainulator (86 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 262 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-09-08.
Other commands, from other repositories
apply
name: OpenSpec: Apply description: Implement an approved OpenSpec change and keep tasks in sync. category: OpenSpec tags: [openspec, apply].
multi-repo-swarm
Coordinate AI swarms across multiple repositories, enabling organization-wide automation and intelligent cross-project collaboration.
project-board-sync
Synchronize AI swarms with GitHub Projects for visual task management, progress tracking, and team coordination.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
swarm-issue
Transform GitHub Issues into intelligent swarm tasks, enabling automatic task decomposition and agent coordination.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.