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/replay)<a href="https://agentmods.dev/commands/grainulation/grainulator/replay"><img src="https://agentmods.dev/badge/commands/grainulation/grainulator/replay/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/replay"><img src="https://agentmods.dev/badge/commands/grainulation/grainulator/replay.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.00727 |
| Opus 5 | $0.00000 | $0.00364 |
| Sonnet 5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
replay 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/replay — Time-Travel Through Sprint Evolution
You are reconstructing the historical evolution of this sprint by recompiling every version of claims.json from git history.
Process
-
Get the git history of claims.json:
git log --oneline claims.jsonThis gives every commit that touched claims.json — the sprint event log.
-
Extract each historical version: For each commit hash:
git show <hash>:claims.json > /tmp/grainulator-replay-<N>.json -
Recompile each version with the current compiler:
grainulator compile --input /tmp/grainulator-replay-<N>.json --output /tmp/grainulator-comp-<N>.json -
Compute deltas between consecutive compilations:
grainulator compile --diff /tmp/grainulator-comp-<N-1>.json /tmp/grainulator-comp-<N>.json -
Identify interesting moments in each delta:
- Phase transitions (define -> research -> prototype -> evaluate)
- First time compilation went "ready"
- Peak conflict count
- Evidence tier jumps (topic going web -> tested)
- Claims added then superseded (the sprint changed its mind)
-
Generate replay HTML: Create
output/replay.html— a self-contained timeline visualization using a dark scroll-snap template. Include:- Frame-by-frame scrubbing (each commit = one frame)
- Highlighted pivotal moments
- Coverage evolution chart
- Summary statistics per frame
-
Print a text summary to the terminal with the key narrative moments.
Version control
Preserve the user’s edits. Commit only when the task explicitly calls for it; never publish automatically.
Tell the user
- How many frames (commits) were found
- The most interesting moments
- Point them to
output/replay.htmlfor the full interactive timeline - Suggest:
/handoffto package this narrative for a successor
Cleanup
Remove temporary files from /tmp after generating the output:
rm -f /tmp/grainulator-replay-*.json /tmp/grainulator-comp-*.json
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 · 80 lines · 0 tokens per session scan A b45bb655b09c
replay 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 727 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
atomic-commits
Analyze staged changes and organize them into intuitive atomic commits following conventional commits.
commit
Creates git commits using conventional commit format with appropriate emojis, following project standards and creating descriptive messages that explain the purpose of changes.
create-pr
Streamlines pull request creation by handling the entire workflow: creating a new branch, committing changes, formatting modified files with Biome, and submitting the PR.
commit
Generate a conventional commit message for staged changes (feat/fix/refactor/...) and run git commit. Refuses if sensitive files are staged.
cm
Stage working tree changes and create a Conventional Commit (no push).
cp
Stage, commit, and push the current branch following git governance rules.