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 skills add alonf/specrew --skill replay-output-doc-verificationgit clone --depth 1 https://github.com/alonf/specrewWrote 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/skills/alonf/specrew/replay-output-doc-verification)<a href="https://agentmods.dev/skills/alonf/specrew/replay-output-doc-verification"><img src="https://agentmods.dev/badge/skills/alonf/specrew/replay-output-doc-verification/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/skills/alonf/specrew/replay-output-doc-verification"><img src="https://agentmods.dev/badge/skills/alonf/specrew/replay-output-doc-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.00255 |
| Opus 5 | $0.00010 | $0.00128 |
| Sonnet 5 | $0.00004 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
replay-output-doc-verification 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 5d 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.
What it actually says
replay-output-doc-verification
Purpose
Prevent user-facing docs from drifting away from the real reviewer replay surfaces.
When to Use
- A README, guide, or runbook shows
specrew reviewoutput or reviewer-index summary lines. - A change adds lockout-cap, routing-fallback, or other handoff-visible state to reviewer artifacts.
- A task explicitly says examples must be verified against actual runtime output instead of handwritten text.
Pattern
- Copy the relevant fixture or project into a scratch workspace inside the repo.
- Run
extensions\specrew-speckit\scripts\scaffold-reviewer-artifacts.ps1for the target iteration. - Run
scripts\specrew.ps1 review --project-path <scratch-project>(orscripts\specrew-review.ps1) and capture the emitted summary/digest lines. - Paste only exact, still-relevant lines into docs; avoid paraphrasing output examples.
- Re-check the documentation file against the captured output before finishing the task.
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.
- 5d ago First seen · 28 lines · 20 tokens per session scan A 0649cbb28f7e
replay-output-doc-verification is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 255 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.