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-codebase-designnpx skills add rodolfochicone/rc-project --skill rc-codebase-designgit 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-codebase-design)<a href="https://agentmods.dev/skills/rodolfochicone/rc-project/rc-codebase-design"><img src="https://agentmods.dev/badge/skills/rodolfochicone/rc-project/rc-codebase-design.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.00036 | $0.01459 |
| Opus 5 | $0.00018 | $0.00730 |
| Sonnet 5 | $0.00007 | $0.00292 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
rc-codebase-design 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 3d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Design
Shared vocabulary for designing deep modules: substantial behaviour behind a small interface, placed at a clean seam, verifiable through that interface. Reach for it whenever code structure is being created or reshaped — the goal is leverage for the caller and locality for the maintainer.
This is a reference to consult, not a session to run. rc-tdd uses seam from here to decide where
tests go; rc-implement uses depth to judge whether a new abstraction earned its place;
rc-code-review's delete-list uses the deletion test. It answers the question those skills come
after: where should this interface live, and how much should it hide?
Not this skill: UI and visual craft is rc-interface-design; service boundaries, data ownership and
10x/100x scaling are a rc-council debate. This one is the everyday module.
Glossary
The terms are the point. Use them literally — they are chosen to avoid words that arrive pre-loaded with someone else's model.
| Term | Means | Say this, not |
|---|---|---|
| module | anything with an interface and an implementation — deliberately scale-agnostic: a function, a class, a package, a slice spanning tiers | unit, component, service |
| interface | everything a caller must know to use it correctly: the type signature plus invariants, ordering constraints, error modes, configuration and performance facts | API, signature — both too narrow |
| implementation | the code inside the module | — |
| depth | leverage at the interface: how much behaviour a caller or a test can exercise per unit of interface they must learn | — |
| seam | a place where you can alter behaviour without editing in that place (Feathers). Where a module's interface lives | boundary — carries DDD baggage |
| adapter | the concrete thing satisfying an interface at a seam. Names a role, not a substance | — |
| leverage | what the caller gains from depth: capability per unit of interface learned | — |
| locality | what the maintainer gains from depth: change, bugs and knowledge concentrate in one place instead of scattering across call sites | — |
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.
- 3d ago First seen · 112 lines · 36 tokens per session scan A a3b29f60bfb8
rc-codebase-design is a skill published in the GitHub repository rodolfochicone/rc-project (19 stars, last pushed 27d ago), licensed MIT. It adds 36 tokens to every session and 1,459 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…