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/rodolfochicone/rc-project/claude-mdgit clone --depth 1 https://github.com/rodolfochicone/rc-projectWrote 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/rodolfochicone/rc-project/claude-md)<a href="https://agentmods.dev/instructions/rodolfochicone/rc-project/claude-md"><img src="https://agentmods.dev/badge/instructions/rodolfochicone/rc-project/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.1 | $0.01450 | $0.01450 |
| Opus 5 | $0.00725 | $0.00725 |
| Sonnet 5 | $0.00290 | $0.00290 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
rc-project 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 6d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides project guidance for coding agents working in this repository.
HIGH PRIORITY
- IF YOU DON'T CHECK SKILLS your task will be invalidated and we will generate rework
- NEVER use workarounds — always use the
no-workaroundsskill for any fix/debug task - NEVER use web search tools to search local project code — for local code, use Grep/Glob instead
- This repository ships plain markdown and small scripts — there is no build, no binary, no
make. "Done" means the content is coherent, every referenced file exists, and frontmatter is valid.
Project Overview
RC is an agent plugin — skills, commands, agents, and hooks — that drives the full lifecycle
of AI-assisted development: optional ideation → PRD → TechSpec → tasks → execution → review →
remediation. It runs inside the agent host; every workflow artifact lives as plain markdown under a
consumer project's .rc/. There is no CLI, no daemon, and no database.
Distribution: the Claude Code plugin marketplace (manifests under .claude-plugin/). The shipped set
stays host-neutral — no component may depend on a host-exclusive tool.
Repository Layout
| Path | Responsibility |
|---|---|
skills/promoted/ |
The 17 shipped skills — the only ones in plugin.json. One directory each: SKILL.md (+ references/, assets/, scripts/) |
skills/stacks/ |
Stack skills, not shipped (rc-rust, rc-axum, rc-sqlx, rc-sveltekit) — loaded by name |
skills/misc/ |
Kept on disk, not shipped. Zero context cost |
commands/ |
Two prompt macros with no skill behind them (/rc-commit-msg, /rc-plano) |
agents/ |
The four council archetypes dispatched by rc-council (pragmatic-engineer, architect-advisor, security-advocate, devils-advocate) |
hooks/ |
Hook manifest (hooks.json) + guard/observe scripts |
.claude-plugin/ |
Claude Code plugin + marketplace manifests |
docs/ |
Operational docs (install channels, plugin usage) |
scripts/ |
plugin-smoke.mjs (the gate), validate-tasks.mjs, lessons.mjs |
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.
- 6d ago First seen · 89 lines · 1,450 tokens per session scan A affc843bbf02
rc-project CLAUDE.md is an instructions file published in the GitHub repository rodolfochicone/rc-project (19 stars, last pushed 1mo ago), licensed MIT. It adds 1,450 tokens to every session, about $0.0072 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
ai-dial-core CLAUDE.md
Claude Code instructions for epam/ai-dial-core, covering claude.md, build & run, set credentials via environment variables, build (skip tests) and run all tests.
ai AGENTS.md
AGENTS.md instructions for vercel/ai, covering agents.md, project overview, repository structure, key directories and core package dependencies.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
InvestSkill GEMINI.md
Gemini CLI instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
technocore-chat AGENTS.md
AGENTS.md instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).