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 skills/rodolfochicone/rc-project/rc-codemapnpx skills add rodolfochicone/rc-project --skill rc-codemapgit 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/skills/rodolfochicone/rc-project/rc-codemap)<a href="https://agentmods.dev/skills/rodolfochicone/rc-project/rc-codemap"><img src="https://agentmods.dev/badge/skills/rodolfochicone/rc-project/rc-codemap.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.00036 | $0.00670 |
| Opus 5 | $0.00018 | $0.00335 |
| Sonnet 5 | $0.00007 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
rc-codemap 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codemap
Maintain a hierarchical, per-directory map of the repository so every exploration-heavy task
starts from a written summary instead of re-scanning source. Each significant directory gets a
codemap.md; a root codemap.md links them. Regeneration is incremental — only directories
that changed since the last run are rebuilt.
Store & staleness
- Maps live as
codemap.mdinside each mapped directory (committed alongside the code). - State lives at
.rc/codemap/last-commit(the git SHA at the last generation). scripts/stale.sh [root]prints the directories that changed since that SHA — or every directory when there is no state yet (first build).scripts/stale.sh --record [root]records the current HEAD after a successful generation. Both fail open: on any git problem they behave as if everything is stale, which is safe.
Workflow
- Scope. Run
scripts/stale.shto get the stale directories. If it returns everything, you're doing a first full build. - Regenerate stale maps. For each stale directory — skipping vendored/generated dirs
(
.git,node_modules,vendor, build output, fixtures) — read its files enough to summarize, then (re)write itscodemap.mdwith: the directory's responsibility, its key files and their roles, notable patterns, and how it connects to sibling directories. Anchor claims to real paths. - Update the index. Refresh the root
codemap.mdso it links every directory map. - Record state. Run
scripts/stale.sh --recordso the next run only rebuilds what changes after this point.
Rules
- A codemap is a map, not a copy: summarize roles and wiring; never paste large code blocks.
- Keep each map short and skimmable — a reader should grasp a directory in under a minute.
- Do not map throwaway directories (build output, vendored deps, fixtures, generated code).
- On a first build of a large repo, map top-down: root + top-level directories first, then descend only into directories that hold real logic.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 56 lines · 36 tokens per session scan A 4cfeeeb1ed55
rc-codemap is a skill published in the GitHub repository rodolfochicone/rc-project (19 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 670 once invoked, about $0.0002 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 skills, from other repositories
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
mle-workflow
Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
verification-loop
A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before claiming it is complete.
content-engine
Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.