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.
npx skills add emiliosheinz/agent-skills --skill create-rfcgit clone --depth 1 https://github.com/emiliosheinz/agent-skillsWrote 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.
[](https://agentmods.dev/skills/emiliosheinz/agent-skills/create-rfc)<a href="https://agentmods.dev/skills/emiliosheinz/agent-skills/create-rfc"><img src="https://agentmods.dev/badge/skills/emiliosheinz/agent-skills/create-rfc/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.
<a href="https://agentmods.dev/skills/emiliosheinz/agent-skills/create-rfc"><img src="https://agentmods.dev/badge/skills/emiliosheinz/agent-skills/create-rfc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00122 | $0.01100 |
| Opus 5 | $0.00061 | $0.00550 |
| Sonnet 5 | $0.00024 | $0.00220 |
| Haiku 4.5 | $0.00012 | $0.00110 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create RFC
Produce one RFC per invocation. An RFC proposes a decision that has not
yet been made and drives stakeholder alignment; if the decision is already
made, use /create-adr to record it. Follow the five-step process — do not
skip Step 2 (validate mandatory fields) or draft before every mandatory
field is present.
Hard rules
- Never invent facts. If a mandatory field is missing, ask. Never fill Background, Assumptions, or Options with plausible-sounding filler.
- Never present a foregone conclusion. If only one option is real, the
document is an ADR, not an RFC — use
/create-adrinstead. - Decision criteria come before options. Criteria written after options look like justification for a preferred choice.
- Include "do nothing" as an explicit option for any significant change.
- Never skip trade-offs. Every option needs honest cons alongside pros.
- Never write in a language other than the user's. Match the language the user is using in this session.
Dispatch
Run the process in order. Read the matching reference file fully before acting — it is the playbook for that step.
| Step | Read | Purpose |
|---|---|---|
| 1 — Gather context | references/process.md |
Ask for topic, impact, urgency, options in mind |
| 2 — Validate mandatory fields | references/process.md |
Ensure title, background, RACI, criteria, options, recommendation are present |
| 3 — Tailor to RFC type | references/types.md |
Technical / Process / Product / Vendor / Policy — extra focus areas |
| 4 — Generate | templates/rfc.md + references/numbering.md |
Fill template, assign number, run quality checklist |
| 5 — Place + next steps | references/process.md |
Confirm file location, print summary + follow-ups |
Run the quality checklist (references/quality.md) before finalizing —
honest options, weighted criteria, quantified background, explicit
assumptions.
Template
Pure markdown scaffold. Load only when writing:
What ships with it
6 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.
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 · 101 lines · 122 tokens per session scan A a8d61b1bc4b9
create-rfc is a skill published in the GitHub repository emiliosheinz/agent-skills (18 stars, last pushed 1mo ago), licensed MIT. It adds 122 tokens to every session and 1,100 once invoked, about $0.0006 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…