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/gotempsh/temps/session-replaygit clone --depth 1 https://github.com/gotempsh/tempsWrote 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/gotempsh/temps/session-replay)<a href="https://agentmods.dev/commands/gotempsh/temps/session-replay"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/session-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.00657 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
session-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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
session-replay command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
session-replay (alias: sessions, replay)
Manage session replay recordings
Subcommands:
list(ls) - List session replays for a projectvisitor- List session replays for a specific visitorshow- Show session metadata (use numeric session ID from list)events- Download or page through all rrweb events for a sessiondelete(rm) - Delete a session replay
session-replay list (alias: ls)
List session replays for a project
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-p, --project <project> |
Project slug or ID | - | No |
--environment-id <id> |
Filter by environment ID | - | No |
--page <n> |
Page number (default: 1) | 1 |
No |
--per-page <n> |
Sessions per page (default: 25, max: 100) | 25 |
No |
--json |
Output raw JSON | - | No |
session-replay visitor
List session replays for a specific visitor
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--page <n> |
Page number (default: 1) | 1 |
No |
--per-page <n> |
Sessions per page (default: 25) | 25 |
No |
--json |
Output raw JSON | - | No |
session-replay show
Show session metadata (use numeric session ID from list)
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output raw JSON | - | No |
session-replay events
Download or page through all rrweb events for a session
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--page <n> |
Page of events to display (default: 1) | 1 |
No |
--limit <n> |
Events per page (default: 50) | 50 |
No |
--output <file> |
Write all events as JSON to a file (skips paged display) | - | No |
--json |
Print all events as JSON to stdout | - | No |
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 · 77 lines · 0 tokens per session scan A 50f494021de1
session-replay is a command published in the GitHub repository gotempsh/temps (712 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 657 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
pr-check
Run all local CI checks before creating a PR.
ci-health
Check all GitHub Actions workflows for failures, create P0 tickets, gate each ticket, and auto-fix safe failures.
ci-status
Real-time GitHub Actions workflow status and recent runs.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
workflow-automation
Integrate AI swarms with GitHub Actions to create intelligent, self-organizing CI/CD pipelines that adapt to your codebase.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.