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 commands/tony/claude-code-riper-5/savegit clone --depth 1 https://github.com/tony/claude-code-riper-5What 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.00007 | $0.00399 |
| Opus 5 | $0.00003 | $0.00199 |
| Sonnet 5 | $0.00001 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade B, and why
save scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Memory-bank MUST be at repository root: Use `git rev-parse --show-toplevel` to find root, then `[ROOT]/.claude/memory-bank/` What it actually says
Saving to Memory Bank
⚠️ Memory Bank Location Requirements
CRITICAL PATH POLICY:
- Memory-bank MUST be at repository root: Use
git rev-parse --show-toplevelto find root, then[ROOT]/.claude/memory-bank/ - NEVER create package-level memory-banks:
packages/*/.claude/memory-bank/❌ - In monorepos: ONE memory-bank at root serves entire project
Correct vs Incorrect Paths
✅ Correct: [ROOT]/.claude/memory-bank/main/session.md (where ROOT = git rev-parse --show-toplevel)
❌ Wrong: [ROOT]/packages/react/.claude/memory-bank/main/session.md
❌ Wrong: packages/react/.claude/memory-bank/main/session.md
I'll save the following information to the branch-aware memory bank:
Context Information
- Date: !
date +%Y-%m-%d - Time: !
date +%H:%M:%S - Branch: !
git branch --show-current - Latest Commit: !
git log -1 --oneline - Working Directory Status: !
git status --short
Memory Content
$ARGUMENTS
Storage Location
The memory will be saved to:
- First run:
git rev-parse --show-toplevelto get repository root - Save to:
[ROOT]/.claude/memory-bank/!git branch --show-current/!date +%Y%m%d-session.md
This ensures memories are:
- Branch-specific (won't conflict when switching branches)
- Date-organized (easy to find recent work)
- Persistent across sessions
- Shareable with team (can be committed if desired)
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.
- 3d ago First seen · 40 lines · 7 tokens per session scan B 80c2aa13e58a
save is a command published in the GitHub repository tony/claude-code-riper-5 (93 stars, last pushed 17d ago), licensed MIT. It adds 7 tokens to every session and 399 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.