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/listgit clone --depth 1 https://github.com/tony/claude-code-riper-5Wrote 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/commands/tony/claude-code-riper-5/list)<a href="https://agentmods.dev/commands/tony/claude-code-riper-5/list"><img src="https://agentmods.dev/badge/commands/tony/claude-code-riper-5/list.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.00005 | $0.00470 |
| Opus 5 | $0.00003 | $0.00235 |
| Sonnet 5 | $0.00001 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade B, and why
list 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 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.
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
Memory Bank Overview
⚠️ 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 for Memory Listing
✅ Correct: [ROOT]/.claude/memory-bank/main/ (where ROOT = git rev-parse --show-toplevel)
❌ Wrong: [ROOT]/packages/react/.claude/memory-bank/main/
❌ Wrong: packages/react/.claude/memory-bank/main/
Current Branch Memories
Branch: !git branch --show-current
!ls -la $(git rev-parse --show-toplevel)/.claude/memory-bank/$(git branch --show-current)/ 2>/dev/null || echo "No memories for current branch"
All Branch Memories
!find $(git rev-parse --show-toplevel)/.claude/memory-bank -type f -name "*.md" 2>/dev/null | head -20 || echo "No memories found"
Memory Organization
[ROOT]/.claude/memory-bank/ (where ROOT = `git rev-parse --show-toplevel`)
├── main/
│ ├── 20250108-session.md
│ └── plans/
│ └── main-20250108-feature.md
├── feature-branch/
│ ├── 20250107-session.md
│ └── reviews/
│ └── feature-branch-20250107-review.md
└── experiment-riper5/
└── 20250108-session.md
Usage Tips
- Memories are organized by branch to prevent conflicts
- Use
/memory:saveto store important context - Use
/memory:recallto retrieve specific memories - Plans and reviews are automatically stored by RIPER modes
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 · 46 lines · 5 tokens per session scan B a3dfe3e81bed
list is a command published in the GitHub repository tony/claude-code-riper-5 (93 stars, last pushed 18d ago), licensed MIT. It adds 5 tokens to every session and 470 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.
Other commands, from other repositories
cleanup-context
You are a memory bank optimization specialist tasked with reducing token usage in the project's documentation system while maintaining all essential information and improving organization.
update-memory-bank
Can you update CLAUDE.md and memory bank files.
dream
Memory consolidation — dedupe, contradiction-check, prune, and re-rank MEMORY.md + CLAUDE.md Project Learnings. Run after major refactors.
init
从零开始 — 触发 dask-CS 跑需求澄清与架构决策，产出 decision-log.
plan
技术规范 — 文件路径、函数签名、变更规格、架构概览、编号清单.
add-expert
Add a new expert to the vault (also covers "build a expert").