rfc-template

rfc-template is a skill for Claude Code from sethdford/claude-skills. It costs 32 tokens per session (681 once invoked), scanned A, original, MIT.

A template for writing an RFC, a document used to propose and review a significant technical change. It covers the problem, proposed solution, design, alternatives, risks, and decision status.

In plain words
What is it for?
Use it to prepare proposals for major changes such as replacing a monolith, introducing a new architecture, or changing an established design pattern.
Why use it?
It gives a structured way to explain why an architectural change is needed and how it should work. This makes trade-offs and open concerns easier for a team to review.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the communication plugin — 7 skills shipped together

Good fit Use it to prepare proposals for major changes such as replacing a monolith, introducing a new architecture, or changing an established design pattern.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sethdford/claude-skills/rfc-template
Install

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.

Any agent
npx skills add sethdford/claude-skills --skill rfc-template
Clone the repo
git clone --depth 1 https://github.com/sethdford/claude-skills

Made for: Claude Code.

Or install communication, the plugin that ships this one along with the rest of its 7 skills.

Wrote 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.

agentmods badge for rfc-template

README.md
[![agentmods](https://agentmods.dev/badge/skills/sethdford/claude-skills/rfc-template/github.svg)](https://agentmods.dev/skills/sethdford/claude-skills/rfc-template)
Your own site
<a href="https://agentmods.dev/skills/sethdford/claude-skills/rfc-template"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/rfc-template/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.

agentmods 80×15 button for rfc-template

Your own site · 80×15
<a href="https://agentmods.dev/skills/sethdford/claude-skills/rfc-template"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/rfc-template.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 681 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00681
Opus 5 $0.00016 $0.00341
Sonnet 5 $0.00006 $0.00136
Haiku 4.5 $0.00003 $0.00068

Measured 10d ago against content hash 6388cfde0e34, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

rfc-template 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.

architect/communication/skills/rfc-template/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

RFC Template

Structure architectural change proposals for collaborative discussion and documented decision-making.

Context

You are proposing a major architectural change. Use RFC (Request for Comments) format to solicit feedback, document rationale, and create audit trail. Read existing architecture, team concerns, and alternatives.

Domain Context

Based on RFC processes (Rust RFCs, Internet RFCs):

  • Problem Statement: What's broken? Why change? Quantify impact (latency, cost, developer productivity).
  • Proposed Solution: How does RFC solve problem? What's the mechanism?
  • Detailed Design: Implementation details. APIs, data structures, state management. Enough to review feasibility.
  • Alternatives Considered: What else did you think about? Why choose this one?
  • Drawbacks and Risks: What could go wrong? Performance impact? Operational complexity? Compatibility issues?

Instructions

  1. RFC Header:

    • Title: "Migrate from Monolith to Microservices"
    • Status: Draft/Discussion/Approved/Implemented
    • Author(s)
    • Date
    • Related Issues/PRs
  2. Problem Section:

    • Current state: Monolithic Node.js app, 500K LOC, hard to test, deploy, scale
    • Pain points: 20-minute builds, deployments block all teams, scaling one service scales everything
    • Impact: 2 hours/week lost to build/deploy, 1 outage/quarter from scaling issues
  3. Proposed Solution:

    • Split into services: API Gateway, Auth, Payment, Orders, Notifications
    • Each service: independent repo, CI/CD, database, deployment
    • Communication: REST APIs, async via RabbitMQ for events
  4. Design Details:

    • Service boundaries (business domain alignment)
    • API contracts (OpenAPI specs)
    • Data consistency model (eventual consistency between services)
    • Deployment strategy (phased, start with payment service)
  5. Alternatives:

    • Monolith + horizontal scaling: Cheaper short-term, doesn't solve coupling
    • Plugins/modular monolith: Simpler than microservices, still shared deployment

Read the full file on GitHub · 65 lines

Changes

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.

  1. 10d ago First seen · 65 lines · 32 tokens per session scan A 6388cfde0e34

Subscribe to this mod's changes

rfc-template is a skill published in the GitHub repository sethdford/claude-skills (40 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 681 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.

Related

Other skills, from other repositories