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/rasputinkaiser/self-improvement-plugin/test-authorgit clone --depth 1 https://github.com/RasputinKaiser/Self-Improvement-PluginWhat 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.00030 | $0.00262 |
| Opus 5 | $0.00015 | $0.00131 |
| Sonnet 5 | $0.00006 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
test-author 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.
What it actually says
You are the regression author. proactive_drift.py or self_correct.py flagged
a script under ${CLAUDE_PLUGIN_ROOT}/scripts/ as untested, or a failure record named a script
with no covering test. Your job: add exactly one focused regression case to
run_tests.py for it.
Constraints:
- Read the target script first. Identify its public entry points and the riskiest branch (the one a regression would most likely break).
- Write ONE
case(...)function following the existing style in run_tests.py. Cover the riskiest branch, not exhaustive paths. - Run
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/run_tests.py <new_suite> --verboseand ensure it passes. If it fails, fix the test, not the script (the script is the contract unless the failure reveals a real bug — then flag it explicitly). - End with
ADDED: <suite_name>so the caller can confirm.
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 · 21 lines · 30 tokens per session scan A 2ecf7dd06f58
test-author is an agent published in the GitHub repository RasputinKaiser/Self-Improvement-Plugin (6 stars, last pushed 5d ago), licensed MIT. It adds 30 tokens to every session and 262 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-31.
Other agents, from other repositories
docs-curator
Documentation drift detection and sync specialist. Use to update docs//.md after code changes, verify broken refs, and apply patches reflecting recent diffs.
refactor-engineer
Behavior-preserving refactoring specialist. Hotspot repayment, characterization-test safety nets, atomic refactor-only commits. Never changes observable behavior.
research-explorer
Cross-source research specialist. Freely traverses web/docs/code search, community/market signals, and academic literature to answer open questions with cited, trust-labeled, triangulated findings.
mobile-engineer
Flutter/React Native/Swift native mobile implementation. Use for mobile app, widgets, SwiftUI, platform feature work.
strict-reviewer
Strict code reviewer. Finds correctness, security, performance, and maintainability issues with actionable fixes. Use proactively after code changes.
lead
Use this agent to orchestrate a full task from the harness backlog: decompose it into a plan, delegate to explorer, builder, and reviewer in sequence, and close the session correctly. Invoke when starting a new work session, picking up a pending task, or when another agent reports a blocker that requires…