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-implementnpx skills add rodolfochicone/rc-project --skill rc-implementgit 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-implement)<a href="https://agentmods.dev/skills/rodolfochicone/rc-project/rc-implement"><img src="https://agentmods.dev/badge/skills/rodolfochicone/rc-project/rc-implement.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.00037 | $0.01523 |
| Opus 5 | $0.00018 | $0.00762 |
| Sonnet 5 | $0.00007 | $0.00305 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
rc-implement 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement
Build what a ticket describes, verify it for real, and record what it taught. One ticket or a whole slug's worth in dependency order — the same cycle either way, so there is one skill rather than one per orchestration style.
Read $CLAUDE_PLUGIN_ROOT/skills/promoted/rc/references/conventions.md first — the .rc resolution,
Serena navigation, the root-cause rule, the verification-evidence bar and the project-memory contract.
1 — Ground
Read the ticket, then the spec it comes from (_techspec.md, _tasks.md) and the ADRs under
adrs/. Consult project memory for the ticket's terms and load the confirmed lessons
(rc-memory section B) — they are design constraints for this scope, not suggestions.
If the ticket, the spec and an ADR contradict each other, stop and report the conflict. Do not guess which one wins. Then reconcile the current working tree before editing: know what is already changed and why.
2 — Build the checklist
Extract every deliverable, acceptance criterion and explicit Validation / Test Plan / Testing
item into one numbered checklist, and print it before implementing so it is visible and trackable.
Capture the concrete pre-change signal that proves the work is not done yet — the failing test, the
missing endpoint, the wrong output. If you cannot reproduce it directly, capture the strongest
available baseline and state the limitation.
The checklist is a gate: mark each item as its evidence appears, and do not enter verification until every item is addressed.
3 — Write the least code that works
You understood the task in steps 1–2. Now write the minimum that satisfies it, stopping at the first rung that holds:
- Does this need to exist? Speculative, or beyond the ticket's contract → record it as a follow-up note, do not build it.
- Already in this codebase? Reuse the helper, type or pattern that already lives here — find it
with
find_symbol/find_referencing_symbolsfirst. Re-implementing what sits a few files over is the most common kind of slop. - Standard library does it? Use it before hand-rolling.
- An already-installed dependency solves it? Use it. Never add a dependency for what a few lines cover.
- Only then write the minimum idiomatic code, mirroring the ticket's
Patterns to Mirror.
What ships with it
2 files 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.
- 4d ago First seen · 130 lines · 37 tokens per session scan A f9f53ea3e32c
rc-implement is a skill published in the GitHub repository rodolfochicone/rc-project (19 stars, last pushed 28d ago), licensed MIT. It adds 37 tokens to every session and 1,523 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
mcporter
List, auth, and call MCP servers/tools from the terminal.
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.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…