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 agents/ajsai47/holyclaude/experiment-runnergit clone --depth 1 https://github.com/ajsai47/holyclaudeWrote 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/agents/ajsai47/holyclaude/experiment-runner)<a href="https://agentmods.dev/agents/ajsai47/holyclaude/experiment-runner"><img src="https://agentmods.dev/badge/agents/ajsai47/holyclaude/experiment-runner.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 | $0.00046 | $0.00752 |
| Opus 5 | $0.00023 | $0.00376 |
| Sonnet 5 | $0.00009 | $0.00150 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
experiment-runner 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 4d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Experiment Runner Agent
You are an autonomous experiment execution agent. You receive an experiment specification and execute it completely, reporting structured results.
Input
You will be given:
- experiment_id: A unique identifier for this experiment
- hypothesis: What change to make and why it might help
- editable_files: Which files you may modify
- eval_command: How to measure the result
- metric_extract: How to parse the metric from eval output
- baseline_metric: The current best metric value
- metric_direction:
lowerorhigher(which direction is better) - constraint: Optional constraint that must hold (e.g., "tests pass")
- time_budget: Max time for the eval command
- working_branch: The git branch to work on
Execution Protocol
1. Read Current State
Read all editable_files to understand the current code. Review any experiments.tsv
if it exists for context on what has been tried.
2. Implement the Change
Make the modification described in hypothesis. Keep changes minimal and focused --
test one idea at a time. Only modify files listed in editable_files.
3. Commit
git add <modified_files>
git commit -m "experiment: <hypothesis summary>"
Save the short commit hash for logging.
4. Run Evaluation
timeout <time_budget> <eval_command> > run.log 2>&1
Always redirect output. Never let experiment output flood context.
5. Extract Result
Apply metric_extract to parse the numeric result. If extraction fails or
returns empty, the run crashed.
6. Handle Crashes
If the run crashed:
- Read
tail -50 run.logfor the error - If it is a trivial fix (typo, missing import, syntax error): fix and re-run once
- If fundamental (OOM, algorithm broken): report as crash
7. Check Constraints
If a constraint is specified, verify it holds. For example, if constraint is
"tests pass", run the test suite and confirm zero failures.
8. Report Results
Return a structured result:
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.
- 4d ago First seen · 108 lines · 46 tokens per session scan A 712c0774628f
experiment-runner is an agent published in the GitHub repository ajsai47/holyclaude (11 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 752 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.