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 randommonicle/claude-skills --skill rerun-before-verdictgit clone --depth 1 https://github.com/randommonicle/claude-skillsWrote 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/randommonicle/claude-skills/rerun-before-verdict)<a href="https://agentmods.dev/skills/randommonicle/claude-skills/rerun-before-verdict"><img src="https://agentmods.dev/badge/skills/randommonicle/claude-skills/rerun-before-verdict/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/randommonicle/claude-skills/rerun-before-verdict"><img src="https://agentmods.dev/badge/skills/randommonicle/claude-skills/rerun-before-verdict.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.00137 | $0.00762 |
| Opus 5 | $0.00068 | $0.00381 |
| Sonnet 5 | $0.00027 | $0.00152 |
| Haiku 4.5 | $0.00014 | $0.00076 |
Grade A, and why
rerun-before-verdict 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 11d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rerun before verdict
A single run tells you where to look, never what is true. This skill governs the moment an observation is about to become a verdict — fixed, dead, worthless, impossible, breakthrough — and requires the controlled re-run that separates the two. Layer: leaf. Admitted by review rather than by the misses log — see Provenance — so candidate-tier until fires accumulate.
The rule
Observations are diagnostic-grade; verdicts need a re-run that isolates the claim. Good news gets the same discipline as bad.
How to apply
- A fix is proven by re-running the case that failed, not by the edit looking right. Diagnose, fix, re-run is one loop; acting on the diagnosis alone ships the theory, not the fix.
- Deadness and value are with/without questions. Run the current system with and without the component before declaring it dead, redundant, or worthless. Apparently dead code can be load-bearing, and an apparent inefficiency can be the price of a correct result — removal on inspection alone is how both get discovered in production.
- A suspiciously good result is a bug until ruled out. Assume measurement error, data leakage, or coincidence first. A finding stays a candidate until at least three consistent datapoints, or one controlled before/after comparison, back it. Celebrating first and checking second is the expensive order.
- "Impossible" is a verdict too. It earns one only after the plausible alternatives have been enumerated and actually tried, not after one failed attempt.
What this skill does not do
It does not interpret individual success signals — verify-the-effect owns proxy-vs-effect for a single operation. It does not judge whether a check is capable of failing (prove-it-can-fail), does not govern claims that arrive from agents or reviewers (findings-are-evidence governs those; this skill governs the run-count behind your own verdict), and does not gate "done" on shipped changes (one-real-ride).
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.
- 11d ago First seen · 58 lines · 137 tokens per session scan A f44fadcbb43d
rerun-before-verdict is a skill published in the GitHub repository randommonicle/claude-skills (23 stars, last pushed 5d ago), licensed Apache-2.0. It adds 137 tokens to every session and 762 once invoked, about $0.0007 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.
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.