rfc

rfc is a skill for Claude Code, Codex from rlajous/claude-code-commands. It costs 14 tokens per session (1,107 once invoked), scanned A, original, MIT.

A command that creates a numbered RFC document from a template. An RFC, or Request for Comments, records a proposed technical change for review.

In plain words
What is it for?
Use it to start a new RFC, assign the next number from existing files, and create the document in the project’s RFC directory.
Why use it?
It removes the need to choose document numbers and fill in standard metadata manually. It also checks and cleans the proposed title.

Skill for Claude CodeCodex

Part of the git-workflow plugin — 21 skills, 8 agents, 2 hooks shipped together

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.

agentmods
npx agentmods add skills/rlajous/claude-code-commands/rfc
Any agent
npx skills add rlajous/claude-code-commands --skill rfc
Clone the repo
git clone --depth 1 https://github.com/rlajous/claude-code-commands

Made for: Claude Code, Codex.

Or install git-workflow, the plugin that ships this one along with the rest of its 21 skills, 8 agents, 2 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/rlajous/claude-code-commands/rfc.svg)](https://agentmods.dev/skills/rlajous/claude-code-commands/rfc)
Your own site
<a href="https://agentmods.dev/skills/rlajous/claude-code-commands/rfc"><img src="https://agentmods.dev/badge/skills/rlajous/claude-code-commands/rfc.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,107 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00014 $0.01107
Opus 5 $0.00007 $0.00553
Sonnet 5 $0.00003 $0.00221
Haiku 4.5 $0.00001 $0.00111

Measured 4d ago against content hash a3faa644c14c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

skills/rfc/SKILL.md · 123 lines

How it starts

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

Cross-runtime: follow runtime compatibility for invocation, delegation, configuration precedence, state paths, and permissions.

You are helping create a new RFC (Request for Comments) document. Your task is to generate a properly numbered RFC file from the template with pre-filled metadata.

Step 1: Parse Arguments

Extract the RFC title from $ARGUMENTS.

  • If $ARGUMENTS is empty or not provided, use the active host user-input mechanism to prompt: "What is the title for this RFC? (e.g., 'add deploy command', 'config schema v2')"
  • Validate the title contains only alphanumeric characters, spaces, and hyphens
  • If invalid characters are found, strip them and confirm with the user

Step 2: Auto-Determine RFC Number

Scan for existing RFC files to determine the next number:

# Find existing RFCs and determine next number
latest=$(ls docs/rfcs/rfc-*.md 2>/dev/null | sort -V | tail -1)
if [ -n "$latest" ]; then
  current=$(basename "$latest" | sed 's/rfc-\([0-9]*\)-.*/\1/')
  next=$((10#$current + 1))
else
  next=1
fi
printf -v rfc_num "%03d" $next

Logic:

  • If no existing RFCs found, start at 001
  • If existing RFCs found, extract the highest NNN from rfc-NNN-*.md and increment by 1
  • Zero-pad to 3 digits (001, 002, ..., 999)

Step 3: Generate Filename

Convert the title to a kebab-case filename:

  • Convert to lowercase
  • Replace spaces with hyphens
  • Remove special characters (keep alphanumeric and hyphens)
  • Collapse multiple hyphens into one
  • Trim leading/trailing hyphens
kebab_title=$(echo "$title" \
  | tr '[:upper:]' '[:lower:]' \
  | sed 's/[^a-z0-9 -]//g' \
  | tr ' ' '-' \
  | sed 's/-\{2,\}/-/g; s/^-//; s/-$//')

Result: rfc-${rfc_num}-${kebab_title}.md

Examples:

  • "Add Deploy Command" -> rfc-001-add-deploy-command.md
  • "Config Schema v2" -> rfc-002-config-schema-v2.md

Step 4: Create Directory

Immediately before creating anything, show the RFC number, title, author, and final file path. Ask for explicit confirmation to create the directory and RFC file. Do not treat automatic skill invocation or title confirmation as approval for the write.

Read the full file on GitHub · 123 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. 4d ago First seen · 123 lines · 14 tokens per session scan A a3faa644c14c

Subscribe to this mod's changes

rfc is a skill published in the GitHub repository rlajous/claude-code-commands (30 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 1,107 once invoked, about $0.0001 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens