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/rcdelacruz/claude-code-agents/claude-mdgit clone --depth 1 https://github.com/rcdelacruz/claude-code-agentsWrote 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/rcdelacruz/claude-code-agents/claude-md)<a href="https://agentmods.dev/instructions/rcdelacruz/claude-code-agents/claude-md"><img src="https://agentmods.dev/badge/instructions/rcdelacruz/claude-code-agents/claude-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.01050 | $0.01050 |
| Opus 5 | $0.00525 | $0.00525 |
| Sonnet 5 | $0.00210 | $0.00210 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
claude-code-agents CLAUDE.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 5d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Development Rules
Core rules for maximizing AI execution accuracy. All instructions must follow this file.
🚨 Most Important Principle: Research OK, Implementation STOP
User approval is mandatory before using any Edit/Write/MultiEdit tools
Reason: To prevent implementations that differ from user intent and ensure correct direction
Mandatory Execution Process
Execution Flow (Required Steps)
- Task decomposition with TodoWrite → Cannot proceed to implementation without it Reason: To structure tasks and enable progress tracking
- Execute rule-advisor → Understand task essence and select appropriate rules Reason: To select appropriate rules and understand task essence
- Use Edit/Write/MultiEdit → User approval is mandatory Reason: Practicing the most important principle (Research OK, Implementation STOP)
- Execute implementation → Cannot complete with quality check errors Reason: To ensure high-quality code
- Count file changes → Auto-stop when threshold exceeded Reason: To get confirmation before impact becomes too large
TodoWrite and Metacognition Integration
Execution Rules:
- When
pending → in_progress: rule-advisor output is mandatory - After rule-advisor execution: Always update TodoWrite (revise task content, priority, granularity)
- Concretize task description based on taskEssence
- Reflect firstActionGuidance in the first task
- Restructure tasks considering warningPatterns
- Using Edit tools without TodoWrite: Stop as rule violation
- When updating task status: Recording implementation details is mandatory (no blanks)
Execution Prerequisites
- rule-advisor output → JSON response must exist
- TodoWrite task → in_progress status must exist
- User approval record → Explicit approval before Edit/Write
- Quality check results → Cannot complete with errors > 0
Prohibited Actions
- Using any type → Causes type check errors Reason: Destroys type safety and causes runtime errors
- Using Edit without TodoWrite → Rule violation Reason: Cannot track progress or ensure quality without task management
- Edit/Write/MultiEdit without approval → Move to approval waiting Reason: To prevent violating the most important principle
- Declaring completion with quality errors → Does not meet completion criteria Reason: To prevent incomplete code from being mixed in
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.
- 5d ago First seen · 110 lines · 1,050 tokens per session scan A c127386db1e0
claude-code-agents CLAUDE.md is an instructions file published in the GitHub repository rcdelacruz/claude-code-agents (2 stars, last pushed 10mo ago), licensed MIT. It adds 1,050 tokens to every session, about $0.0052 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).