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 instructions/tony/claude-code-riper-5/agents-mdgit 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/instructions/tony/claude-code-riper-5/agents-md)<a href="https://agentmods.dev/instructions/tony/claude-code-riper-5/agents-md"><img src="https://agentmods.dev/badge/instructions/tony/claude-code-riper-5/agents-md.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.02726 | $0.02726 |
| Opus 5 | $0.01363 | $0.01363 |
| Sonnet 5 | $0.00545 | $0.00545 |
| Haiku 4.5 | $0.00273 | $0.00273 |
Grade A, and why
claude-code-riper-5 AGENTS.md 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — claude-code-riper-5
Git Commit Standards
Format commit messages as:
Scope(type[detail]): concise description
why: Explanation of necessity or impact.
what:
- Specific technical changes made
- Focused on a single topic
Keep the subject ≤50 chars (excluding any trailing (#NN) PR ref); wrap
body lines at ≤72 chars. Separate the why: and what: blocks with a
blank line.
Common commit types:
- feat: New features or enhancements
- fix: Bug fixes
- refactor: Code restructuring without functional change
- docs: Documentation updates
- chore: Maintenance (dependencies, tooling, config)
- test: Test-related updates
- style: Code style and formatting
- ai(rules[AGENTS]): AI rule updates
- ai(claude[rules]): Claude Code rules (CLAUDE.md)
- ai(claude[command]): Claude Code command changes
Documentation Standards
Code Blocks
Code blocks are paste-and-run units: pasting one block runs exactly one intended action. Doctests and other executed examples are exempt — the test suite runs them, nobody pastes them.
- One command per block. Multiple steps may share a block only when
explicitly chained with
&&,;, or\continuations — the chain is then one logical command. - Explanations go in prose above the block, never as
#comments inside it. - Command menus are per-command blocks with prose lead-ins, not tables.
- Shell commands use the
consoletag with a$prefix. This separates interactive commands from scripts and enables prompt-aware copy. - Split long commands with
\— one flag or flag+value pair per indented continuation line, positional arguments last.
Good:
Show the last ten commits as a graph:
$ git log \
--max-count=10 \
--graph \
--oneline
Bad:
# Show the last ten commits as a graph
$ git log --max-count=10 --graph --oneline
Comments earn their maintenance cost
A comment ships only if it passes all three gates. Fail any: delete or rewrite. Borderline: delete — borderline means the information is reconstructible, which is what makes deletion cheap.
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 · 297 lines · 2,726 tokens per session scan A 364ba72e9205
claude-code-riper-5 AGENTS.md is an instructions file published in the GitHub repository tony/claude-code-riper-5 (93 stars, last pushed 19d ago), licensed MIT. It adds 2,726 tokens to every session, about $0.0136 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 instructions, from other repositories
awesome-claude-code-subagents CLAUDE.md
Claude Code instructions for VoltAgent/awesome-claude-code-subagents, covering claude.md, project overview, repository structure, subagent file format and communication protocol.
daisyui code_generation_with_git.instructions.md
Instructions for saadeghi/daisyui, covering activation, initial setup, development loop, error handling and session end.
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.
ai-git-commiter CLAUDE.md
Instructions for zdt1013/ai-git-commiter, covering ai git commiter, 项目结构, 技术栈, 常用命令 and 安装依赖.
orkid CLAUDE.md
Claude Code instructions for tweakoz/orkid, covering orkid — repo-wide agent law and commits.
deploystack copilot-instructions.md
Copilot instructions for deploystackio/deploystack, covering github copilot instructions for deploystack, project context, commit message requirements, required scopes and scope selection rules.