agentmods.dev

create-rfc

create-rfc is a skill for Claude Code, Codex from jpoutrin/product-forge. It costs 15 tokens per session (626 once invoked), scanned A, original, MIT.

A command for creating a new RFC, or Request for Comments, which is a document used to propose and review a technical decision. It assigns the next number, creates the expected folders and file, and fills in basic metadata.

In plain words
What is it for?
Use it to start a numbered draft RFC from a short title, create its filename and directory, and record its initial status and dates.
Why use it?
It removes repetitive setup and keeps new technical proposals in a predictable location and format. This makes RFCs easier for a team to find and manage.

Skill for Claude CodeCodex

Part of the devops-data plugin — 17 skills, 4 agents shipped together

not rated 15 6mo ago A scan 15 tokens original MIT
View the source file jpoutrin/product-forge
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/jpoutrin/product-forge/create-rfc
Any agent
npx skills add jpoutrin/product-forge --skill create-rfc
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code, Codex.

Or install devops-data, the plugin that ships this one along with the rest of its 17 skills, 4 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/create-rfc.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/create-rfc)
Your own site
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/create-rfc"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/create-rfc.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 626 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.00015 $0.00626
Opus 5 $0.00008 $0.00313
Sonnet 5 $0.00003 $0.00125
Haiku 4.5 $0.00002 $0.00063

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

Security

Grade A, and why

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

plugins/devops-data/skills/create-rfc/SKILL.md · 98 lines

How it starts

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

create-rfc

Category: Technical Architecture

Usage

/create-rfc <rfc-title>

Arguments

  • <rfc-title>: Required - Short descriptive title for the RFC (will be kebab-cased for filename)

Execution Instructions

When this command is run, Claude Code should:

  1. Determine RFC Number

    • Scan rfcs/ directory (all subdirectories) for existing RFC files
    • Find highest RFC number (RFC-XXXX pattern)
    • Increment by 1 for new RFC
    • If no RFCs exist, start with RFC-0001

  2. Create Directory Structure (if not exists)

    rfcs/
├── draft/
├── review/
├── approved/
│   └── in-progress/
├── completed/
└── archive/

  3. Generate RFC File

    • Convert title to kebab-case: "API Gateway Selection" → "api-gateway-selection"
    • Create file: rfcs/draft/RFC-XXXX-<kebab-title>.md
    • Use template from skill references

  4. Populate Metadata

    • Set rfc_id to new number
    • Set title from argument
    • Set status to DRAFT
    • Set created and last_updated to today's date
    • Leave author for user to fill

  5. Confirm Creation

    Created RFC-XXXX: <title>

Location: rfcs/draft/RFC-XXXX-<kebab-title>.md
Status: DRAFT

Next steps:
1. Fill in the Overview and Problem Statement sections
2. Define your Evaluation Criteria before analyzing options
3. Analyze at least 2 options objectively
4. When ready for review: /rfc-status RFC-XXXX --set REVIEW

Template Reference

Use the template from: plugins/devops-data/skills/rfc-specification/references/rfc-template.md

Example Usage

/create-rfc API Gateway Selection

Creates: rfcs/draft/RFC-0001-api-gateway-selection.md

/create-rfc Database Migration Strategy

Creates: rfcs/draft/RFC-0002-database-migration-strategy.md

Validation

  • Title must be provided (not empty)
  • Title should be 2-6 words for clarity
  • Warn if similar RFC already exists (fuzzy match on title)

Error Handling

Read the full file on GitHub · 98 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 · 98 lines · 15 tokens per session scan A acecee4c8564

Subscribe to this mod's changes

create-rfc is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 626 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