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/merge)<a href="https://agentmods.dev/commands/grainulation/grainulator/merge"><img src="https://agentmods.dev/badge/commands/grainulation/grainulator/merge/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/merge"><img src="https://agentmods.dev/badge/commands/grainulation/grainulator/merge.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.00620 |
| Opus 5 | $0.00000 | $0.00310 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
merge 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/merge — Combine Claim Sets Across Sprints
You are merging claims from another sprint into the current one. This is for when two teams researched the same problem independently and need to combine their findings.
Process
-
Parse the argument: The user provides a path to another sprint's claims.json.
- Example:
/merge ../auth-sprint/claims.json - If no path given, ask for it.
- Example:
-
Validate both claim sets:
- Read the current
claims.json - Read the incoming claims file
- Validate both against the compiler schema:
grainulator compile --input <incoming-path> --output /tmp/grainulator-merge-incoming.json
- Read the current
-
Determine the sprint slug: Derive from the incoming sprint's
meta.question. -
Resolve ID collisions: Prefix all incoming claim IDs with the sprint slug:
r001->auth-r001- Also update all
conflicts_withandresolved_byreferences.
-
Align topics: Present probable topic mappings for user confirmation.
-
Detect cross-sprint conflicts and identify evidence upgrades.
-
Import each supported claim through Grainulator mutation tools, preserving IDs or allocating collision-free IDs and recording source provenance, then compile:
grainulator compile --summary
Version control
Preserve the user’s edits. Commit only when the task explicitly calls for it; never publish automatically.
Tell the user
- How many claims were merged
- Topic alignment results
- Cross-sprint conflicts detected
- Suggest:
/resolvefor conflicts,/blind-spotfor cross-sprint gaps
Cleanup
rm -f /tmp/grainulator-merge-*.json
$ARGUMENTS
Managed evidence and completion
Use Grainulator tools or CLI for claim mutations; do not directly rewrite managed ledger files. Evidence tiers describe actual support, not the connector used. Investigate only material gaps and finish the requested artifact without fixed claim or pass quotas.
Next-step output
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.
- 3d ago First seen · 65 lines · 0 tokens per session scan A 721ab5ca22ba
merge is a command published in the GitHub repository grainulation/grainulator (86 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 620 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.