agentmods.dev

replay-run

replay-run is a command for Claude Code from ololand-ai/ololand-plugins. It costs 64 tokens per session (924 once invoked), scanned A, original, Apache-2.0.

A command for rerunning an existing OloLand agent run using either the current tools and skills or the exact original methodology files. OloLand is an agent-run system with recorded inputs and results.

In plain words
What is it for?
Use it to replay a recorded run for compliance or review, choosing current-skill or byte-for-byte mode; it requires an administrator or compliance role.
Why use it?
It helps verify that a past result can be reproduced or compare how it changes under the current setup.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ololand-dd plugin — 22 skills, 52 commands, 3 agents shipped together

not rated 0repo 4d ago A scan 64 tokens original Apache-2.0

Good fit Use it to replay a recorded run for compliance or review, choosing current-skill or byte-for-byte mode; it requires an administrator or compliance role.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ololand-ai/ololand-plugins/replay-run
View source ↗ ololand-ai/ololand-plugins
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ololand-ai/ololand-plugins

Made for: Claude Code.

Or install ololand-dd, the plugin that ships this one along with the rest of its 22 skills, 52 commands, 3 agents.

Wrote 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.

agentmods badge for replay-run

README.md
[![agentmods](https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/replay-run.svg)](https://agentmods.dev/commands/ololand-ai/ololand-plugins/replay-run)
Your own site
<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/replay-run"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/replay-run.svg" alt="Measured on agentmods" height="20"></a>
Per session 64 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 924 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.00924
Opus 5 $0.00032 $0.00462
Sonnet 5 $0.00013 $0.00185
Haiku 4.5 $0.00006 $0.00092

Measured 8d ago against content hash c6b1568429a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

replay-run 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 8d 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.

plugins/ololand-dd/commands/replay-run.md · 65 lines

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.

/replay-run

You are enqueueing a replay of an existing OloLand agent run. The original run's root_prompt_snapshot is replayed against either the current harness + skill catalog (current_skills) or the original methodology bytes (byte_for_byte).

This command requires admin or compliance role. Non-privileged users will get error_code: "insufficient_role".

Required inputs

  1. run_id — the agent_runs row to replay. Confirm from the user that this is the run they want replayed; replays cost credits and a Celery worker.

Optional:

  • mode — current_skills (default) or byte_for_byte. See "When to use which mode" below.
  • comment — short reviewer note stored on the replay (e.g. "Re-run after grader fix 2026-05-17"). Strongly recommended for audit trail.

Action

  1. (Optional but recommended) Call mcp__ololand__get_agent_run first to confirm the run is replayable. The user should see at least: agent_name, model_version, status, started_at, entry_point. If root_prompt_snapshot is not present, the replay will fail with error_code: "no_snapshot" — surface that pre-emptively.

  2. Call mcp__ololand__replay_agent_run with run_id, mode, optional comment.

  3. On success, surface:

    Replay queued
  Replay run id:  <replay_run_id>
  Parent run id:  <parent_run_id>
  Status:         queued
  Compare:        <comparison_url>

    Tell the user to poll mcp__ololand__get_agent_run <replay_run_id> for completion. Typical end-to-end latency: 30–180 seconds depending on the original run's iteration count.

  4. On error, surface the error_code verbatim and the explanation:

    • not_found — wrong run_id.
    • access_denied — run belongs to a different company.
    • insufficient_role — user is not admin/compliance.
    • no_snapshot — original run pre-dates snapshot capture (pre-2026-05-14 runs).
    • bad_request — invalid mode.
    • dispatch_failed — Celery rejection; the replay row is marked error.

Read the full file on GitHub · 65 lines

Changes

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.

  1. 8d ago First seen · 65 lines · 64 tokens per session scan A c6b1568429a1

Subscribe to this mod's changes

replay-run is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 4d ago), licensed Apache-2.0. It adds 64 tokens to every session and 924 once invoked, about $0.0003 per session on Opus 5. 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-08-31.

Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

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.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

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.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens