Borrowing it
Nothing to install: this file belongs to loonghao/auroraview. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/loonghao/auroraview/main/.codebuddy/skills/rfc-creator/SKILL.mdgit clone --depth 1 https://github.com/loonghao/auroraviewWrote 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/loonghao/auroraview/rfc-creator)<a href="https://agentmods.dev/skills/loonghao/auroraview/rfc-creator"><img src="https://agentmods.dev/badge/skills/loonghao/auroraview/rfc-creator/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/loonghao/auroraview/rfc-creator"><img src="https://agentmods.dev/badge/skills/loonghao/auroraview/rfc-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.01582 |
| Opus 5 | $0.00031 | $0.00791 |
| Sonnet 5 | $0.00012 | $0.00316 |
| Haiku 4.5 | $0.00006 | $0.00158 |
Grade A, and why
rfc-creator 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 10d 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RFC Creator
This skill guides the creation of RFC (Request for Comments) documents for technical proposals.
When to Use
- Proposing a new feature or capability
- Planning architectural changes
- Introducing breaking changes
- Major refactoring proposals
- New configuration formats or APIs
- Integration with external systems
RFC Document Structure
Standard Sections
- Header - Metadata (status, author, date, target version)
- 摘要/Summary - Brief overview of the proposal
- 动机/Motivation - Why this change is needed
- 设计方案/Design - Detailed technical design
- 向后兼容性/Backward Compatibility - Migration and compatibility considerations
- 实现计划/Implementation Plan - Phased implementation roadmap
- 参考资料/References - Related documents and resources
- 更新记录/Changelog - Document revision history
Step 1: Create RFC Directory
docs/rfcs/
├── NNNN-short-title.md # Main RFC document
└── NNNN-implementation-tracker.md # Implementation progress tracker (optional)
RFC numbers are assigned sequentially: 0001, 0002, etc.
Step 2: RFC Header Template
# RFC NNNN: Title
> **状态**: Draft | Review | Accepted | Implemented | Rejected
> **作者**: author name/team
> **创建日期**: YYYY-MM-DD
> **目标版本**: vX.Y.Z
Status Definitions
| Status | Description |
|---|---|
| Draft | Initial proposal, open for major changes |
| Review | Ready for team review and feedback |
| Accepted | Approved for implementation |
| Implemented | Fully implemented and released |
| Rejected | Not accepted (with documented reasons) |
Step 3: Write the RFC Content
3.1 Summary Section
## 摘要
[One paragraph describing what this RFC proposes and its main benefits]
3.2 Motivation Section
## 动机
### 当前状态分析
[Describe current limitations or problems]
### 行业趋势对比
[Compare with similar tools/approaches in the industry]
| 工具 | 特点 | 可借鉴 |
|------|------|--------|
| Tool A | Feature X | Learning Y |
### 需求分析
[List specific requirements this proposal addresses]
1. **Requirement 1** - Description
2. **Requirement 2** - Description
What ships with it
2 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.
- 10d ago First seen · 290 lines · 62 tokens per session scan A a8e86f782b40
rfc-creator is a skill published in the GitHub repository loonghao/auroraview (44 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 1,582 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.
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…