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/agoldian/claudenv/rollback-analyzergit clone --depth 1 https://github.com/AGoldian/claudenvWhat 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.00027 | $0.00207 |
| Opus 5 | $0.00014 | $0.00103 |
| Sonnet 5 | $0.00005 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
rollback-analyzer 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 analyze past hypothesis branches to help the parent agent avoid repeating mistakes.
Your workflow
- List branches:
git branch -l "claudenv/*" - For each relevant branch, show:
git log --oneline <parent>..claudenv/<name> - Read key changed files:
git diff <parent>...claudenv/<name> --stat - Summarize: what was tried, what failed, what can be learned
Output format
For each hypothesis branch:
- Branch: claudenv/
- Goal:
- Changes:
- Result: SUCCESS/FAILURE
- Lesson:
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 · 23 lines · 27 tokens per session scan A 044bfb2886ef
rollback-analyzer is an agent published in the GitHub repository AGoldian/claudenv (10 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 207 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-08-31.
Other agents, from other repositories
release-bundle-testing
Rozenite is a development tool. Whatever a project wires into its bundler config, a release build must ship none of our code. @rozenite/test-utils provides the bench that proves it, and every plugin owns a Vitest suite in src/tests/release-bundle.test.ts that uses it.
e2e-testing
pnpm expo run:ios pnpm expo run:android.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
worktree-collaboration
This document defines the default collaboration protocol for multiple Agents working on Vibelution in parallel.
domain
This document defines the canonical domain language for Vibelution so architecture work can use stable names for the same concepts. It is intentionally small: add terms when they become load-bearing in design or tests.
engagement-partner
Senior strategy consulting partner who scopes business problems, synthesizes multiple analytical workstreams, and delivers board-ready strategic recommendations. Use this skill when someone needs a senior strategic advisor, asks for 'the big picture', wants executive-level synthesis, says things like 'what should we…