Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rodolfochicone/rc-project/plugin install rcWrote 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-tickets)<a href="https://agentmods.dev/skills/rodolfochicone/rc-project/rc-tickets"><img src="https://agentmods.dev/badge/skills/rodolfochicone/rc-project/rc-tickets/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rodolfochicone/rc-project/rc-tickets"><img src="https://agentmods.dev/badge/skills/rodolfochicone/rc-project/rc-tickets.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.01864 |
| Opus 5 | $0.00015 | $0.00932 |
| Sonnet 5 | $0.00006 | $0.00373 |
| Haiku 4.5 | $0.00003 | $0.00186 |
Grade A, and why
rc-tickets 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 10d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tickets
Decompose a spec into tickets an executor can implement in isolation, each carrying enough context that nobody has to grep the repo to start. A roadmap is the same object at a coarser grain — a list of phases, each of which later decomposes into tickets — so both live here.
Read $CLAUDE_PLUGIN_ROOT/skills/promoted/rc/references/conventions.md first.
Field definitions are in references/task-context-schema.md; the ticket body structure is
references/task-template.md; the roadmap format is references/roadmap-format.md.
1 — Load context
The allowed type values are frontend, backend, docs, test, infra, refactor, chore,
bugfix. (These used to be overridable from .rc/config.toml, which was the retired CLI's config
file — nothing reads it now. A project needing a different set edits this list.)
Read _prd.md, _techspec.md and the ADRs under .rc/tasks/<slug>/adrs/. Then:
- No
_techspec.md— warn that tickets will be coarser, derive them from the PRD's functional requirements and user stories, lean harder on codebase exploration for implementation detail, and call out the gaps explicitly in the ticket body instead of inventing specifics. - Neither document — stop and ask the user to create at least one first.
Spawn read-only subagents to explore the codebase for the files to create or modify, the test patterns and the coding conventions in play.
2 — Challenge scope, then decompose
The spec already applied YAGNI to the architecture; here the guard is ticket scope. Before turning a requirement into a ticket, ask whether it needs to exist in this delivery or is speculative, and whether step 1's exploration already found something that covers it. Drop speculative tickets; merge ones that only scaffold "for later". If the spec deliberately cut a component, do not reintroduce it as a ticket. Never silently remove work the PRD explicitly requests — when something looks like YAGNI but sits inside PRD scope, keep it and flag it at the approval gate.
What ships with it
3 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.
- 10d ago First seen · 154 lines · 31 tokens per session scan A f93b6a3b5ef6
rc-tickets is a skill published in the GitHub repository rodolfochicone/rc-project (19 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,864 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
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.
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
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.
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.
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.