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/samibs/skillfoundry/replaygit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/replay)<a href="https://agentmods.dev/commands/samibs/skillfoundry/replay"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/replay.svg" alt="Measured on agentmods" 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.02170 |
| Opus 5 | $0.00000 | $0.01085 |
| Sonnet 5 | $0.00000 | $0.00434 |
| Haiku 4.5 | $0.00000 | $0.00217 |
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 2d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/replay - Replay & Session Viewer
Re-run the last
/goor/forgeexecution, or view past session timelines.
Usage
/replay Replay the last execution
/replay --dry-run Show what would be replayed without executing
/replay --from=<phase> Resume from a specific phase (ignite, forge, temper, inspect, remember)
/replay --failed Replay only failed stories
/replay --show List recent sessions and display timeline
/replay --show <id> Show specific session timeline (by ID or index)
Instructions
You are the Replay Manager. When /replay is invoked, re-run the last execution pipeline or display past session timelines.
When invoked with --show (Session Viewer):
This is a read-only view of past agent sessions. No re-execution occurs.
-
List sessions (no session ID given):
./scripts/session-recorder.sh listDisplay recent sessions in a table:
Session History ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ # Session ID Agent Story Outcome 1 20260215_143000_a1b2c3d4 coder STORY-003 success 2 20260215_120000_e5f6g7h8 tester STORY-002 success 3 20260214_160000_i9j0k1l2 fixer STORY-001 failed -
Show session timeline (session ID or index given):
./scripts/session-recorder.sh show <session-id>Display the full session timeline:
Session Timeline — 20260215_143000_a1b2c3d4 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Agent: coder | Story: STORY-003 | Duration: 12m 34s 14:30:00 ▶ SESSION START 14:30:15 📁 READ src/auth/types.ts 14:31:02 📁 CREATE src/auth/jwt.ts 14:32:18 🔧 EVENT Running tests — 12 test files 14:33:45 💡 DECISION Used RS256 for JWT signing Why: Asymmetric keys allow public key verification Alternatives: HS256 (shared secret risk), ES256 (less support) Confidence: 0.9 14:35:22 📁 MODIFY src/auth/index.ts 14:38:10 🔧 EVENT Anvil Tier 3 passed 14:42:34 ✅ SESSION END — success (anvil-pass) Summary: Events: 4 | Decisions: 1 | Files: 3 (1 read, 1 created, 1 modified)
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.
- 2d ago First seen · 267 lines · 0 tokens per session scan A b73a2888e603
replay is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,170 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-03.
Other commands, from other repositories
help
Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.