What is octocode-rfc-generator?

A structured decision document for significant software changes, such as architecture proposals, migrations, or rollout plans. It compares options and records the chosen approach, evidence, requirements, and checks.

Use it to write or review RFCs—documents that explain and justify an engineering decision—before implementing a consequential change.

It prevents teams from coding before they agree on the problem, trade-offs, scope, and way to verify the result.

octocode-rfc-generator — Skill for Claude Code and Codex by bgauryy

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 bgauryy/octocode --skill octocode-rfc-generator

Clone the repo

git clone --depth 1 https://github.com/bgauryy/octocode

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bgauryy/octocode/octocode-rfc-generator/github.svg)](https://agentmods.dev/skills/bgauryy/octocode/octocode-rfc-generator)

Your own site

<a href="https://agentmods.dev/skills/bgauryy/octocode/octocode-rfc-generator"><img src="https://agentmods.dev/badge/skills/bgauryy/octocode/octocode-rfc-generator/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bgauryy/octocode/octocode-rfc-generator"><img src="https://agentmods.dev/badge/skills/bgauryy/octocode/octocode-rfc-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 953 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00060	$0.00953
Opus 5	$0.00030	$0.00477
Sonnet 5	$0.00012	$0.00191
Haiku 4.5	$0.00006	$0.00095

Measured 12d ago against content hash 1a1c08851a2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

octocode-rfc-generator 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 12d 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/octocode-rfc-generator/SKILL.md · 42 lines

How it starts

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

Octocode RFC Generator

Produce evidence-backed decisions that an implementer and reviewer can execute. Flow: UNDERSTAND → RESEARCH → PREREQUISITES → COMPARE → WRITE → CLOSE QUESTIONS → KPI → VALIDATE → DELIVER. For existing RFCs, run REASSESS (see references/workflow.md § Reassess existing RFCs) instead of WRITE — audit against live code, not prior checkboxes.

Lobby rules

Skip RFC mode for trivial edits. Ask one focused question when uncertainty changes shape, owner, scope, or decision criteria.
Compare at least two alternatives, including do-nothing, unless the user explicitly requests one implementation plan.
Recommendations require verifiable facts; cite exact anchors and commands/checks that actually ran.
RFC.md owns goals, scope, and decision. Other files link to its anchors rather than restating them.
Resolve every open question with evidence or an explicit deferral; no recommendation may rest on an uncertain claim.
Order implementation by dependency, not estimates; bind requirements to acceptance and verification.
Reviewing, rating, or cleaning up .octocode/rfc/ (delete/implemented/fixed calls) always requires a dated ## Audit Reasoning block written into the RFC itself, backed by fresh reads of the live code.
Never assert RFC status from memory or from another RFC's claims.
Stop when: the change is a trivial one-file edit (route to octocode-research); a brainstorming handoff is marked Prototype First, Narrow, Park, or not ready; uncertainty changes artifact shape, owner, scope, or tradeoff priority; two research attempts fail (state what is known and ask for direction); scope needs splitting into separate RFCs or phases; an unresolved blocker would have to be assumed satisfied; or a save, delete, or archive under .octocode/rfc/ awaits explicit approval.

Artifact route

Small, reversible, single-package work: produce only RFC.md with plan, acceptance, and inline references.
Otherwise, after save approval, create <workspace>/.octocode/rfc/{name}/: RFC.md (decide), PREREQUISITES.md (ready, existing code only), IMPLEMENTATION.md (build), KPI.md (verify), and RESOURCES.md (source appendix).

Read the full file on GitHub · 42 lines

Files

What ships with it

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

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.

12d ago First seen · 42 lines · 60 tokens per session scan A 1a1c08851a2a

Subscribe to this mod's changes

octocode-rfc-generator is a skill published in the GitHub repository bgauryy/octocode (932 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 953 once invoked, about $0.0003 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.

Planning ai claude-ai cursor-ai development mcp modelcontextprotocol

octocode-rfc-generator

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Octocode RFC Generator

Lobby rules

Artifact route

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

create-handler

architecture-docs

component-creation

fix-tests

code-review

infrastructure