rfc-status

rfc-status is a skill for Claude Code from jpoutrin/product-forge. It costs 13 tokens per session (1,250 once invoked), scanned A, original, MIT.

A tool for viewing or changing an RFC's status. An RFC, or request for comments, is a document used to propose and review a technical decision through defined stages.

In plain words
What is it for?
Use it to find an RFC, view its details, change its lifecycle status, assign reviewers, and add comments about the decision.
Why use it?
It makes the decision process visible by showing the document, its reviewers, comments, and current stage. It also provides a consistent way to record status changes.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

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

Good fit Use it to find an RFC, view its details, change its lifecycle…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jpoutrin/product-forge/rfc-status
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 jpoutrin/product-forge --skill rfc-status
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/rfc-status.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/rfc-status)
Your own site
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/rfc-status"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/rfc-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,250 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.00013 $0.01250
Opus 5 $0.00006 $0.00625
Sonnet 5 $0.00003 $0.00250
Haiku 4.5 $0.00001 $0.00125

Measured 7d ago against content hash 54674b70aa4b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

rfc-status 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 7d 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/rfc-status/SKILL.md · 196 lines

How it starts

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

rfc-status

Category: Technical Architecture

Usage

/rfc-status <rfc-id> [options]

Arguments

  • <rfc-id>: Required - RFC identifier (e.g., RFC-0042 or just 0042)

Options

Option Description
--set <status> Transition to new status
--reviewer <name> Add or update reviewer
--comment <text> Add status change comment

Valid Statuses

  • DRAFT - Initial writing
  • REVIEW - Open for feedback
  • APPROVED - Decision made
  • IN_PROGRESS - Implementation started
  • COMPLETED - Implementation finished
  • REJECTED - Proposal declined
  • ABANDONED - Author withdrew
  • SUPERSEDED - Replaced by newer RFC

Execution Instructions

View Status (no --set)

When viewing an RFC:

  1. Find the RFC file

    • Search all rfcs/ subdirectories
    • Match by RFC ID in filename or frontmatter
  2. Display RFC Details

RFC-0042: Database Migration Strategy
======================================

Status:      REVIEW
Author:      Jane Doe
Created:     2025-12-01
Updated:     2025-12-05
Location:    rfcs/review/RFC-0042-database-migration-strategy.md

Reviewers:
  - Alice Chen: approved (2025-12-04)
  - Bob Smith: pending
  - Carol Wu: in-progress

Overview:
  [First 2-3 sentences of the Overview section]

Valid Transitions:
  → APPROVED  (requires all reviewers approved)
  → DRAFT     (needs revision)
  → REJECTED  (proposal declined)

Commands:
  /rfc-status RFC-0042 --set APPROVED
  /rfc-status RFC-0042 --reviewer "Bob Smith:approved"

Update Status (with --set)

When updating status:

  1. Validate Transition

    Valid transitions:

    From To
    DRAFT REVIEW, ABANDONED
    REVIEW APPROVED, REJECTED, DRAFT
    APPROVED IN_PROGRESS, SUPERSEDED
    IN_PROGRESS COMPLETED, SUPERSEDED
    Any SUPERSEDED (with link to new RFC)
  2. Perform Pre-transition Checks

    For REVIEW → APPROVED:

    • Warn if not all reviewers approved
    • Require at least one approved reviewer

Read the full file on GitHub · 196 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. 7d ago First seen · 196 lines · 13 tokens per session scan A 54674b70aa4b

Subscribe to this mod's changes

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

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens