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 sethdford/claude-skills --skill rfc-templategit clone --depth 1 https://github.com/sethdford/claude-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/sethdford/claude-skills/rfc-template)<a href="https://agentmods.dev/skills/sethdford/claude-skills/rfc-template"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/rfc-template/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/sethdford/claude-skills/rfc-template"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/rfc-template.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.00032 | $0.00681 |
| Opus 5 | $0.00016 | $0.00341 |
| Sonnet 5 | $0.00006 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
rfc-template 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RFC Template
Structure architectural change proposals for collaborative discussion and documented decision-making.
Context
You are proposing a major architectural change. Use RFC (Request for Comments) format to solicit feedback, document rationale, and create audit trail. Read existing architecture, team concerns, and alternatives.
Domain Context
Based on RFC processes (Rust RFCs, Internet RFCs):
- Problem Statement: What's broken? Why change? Quantify impact (latency, cost, developer productivity).
- Proposed Solution: How does RFC solve problem? What's the mechanism?
- Detailed Design: Implementation details. APIs, data structures, state management. Enough to review feasibility.
- Alternatives Considered: What else did you think about? Why choose this one?
- Drawbacks and Risks: What could go wrong? Performance impact? Operational complexity? Compatibility issues?
Instructions
-
RFC Header:
- Title: "Migrate from Monolith to Microservices"
- Status: Draft/Discussion/Approved/Implemented
- Author(s)
- Date
- Related Issues/PRs
-
Problem Section:
- Current state: Monolithic Node.js app, 500K LOC, hard to test, deploy, scale
- Pain points: 20-minute builds, deployments block all teams, scaling one service scales everything
- Impact: 2 hours/week lost to build/deploy, 1 outage/quarter from scaling issues
-
Proposed Solution:
- Split into services: API Gateway, Auth, Payment, Orders, Notifications
- Each service: independent repo, CI/CD, database, deployment
- Communication: REST APIs, async via RabbitMQ for events
-
Design Details:
- Service boundaries (business domain alignment)
- API contracts (OpenAPI specs)
- Data consistency model (eventual consistency between services)
- Deployment strategy (phased, start with payment service)
-
Alternatives:
- Monolith + horizontal scaling: Cheaper short-term, doesn't solve coupling
- Plugins/modular monolith: Simpler than microservices, still shared deployment
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 · 65 lines · 32 tokens per session scan A 6388cfde0e34
rfc-template is a skill published in the GitHub repository sethdford/claude-skills (40 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 681 once invoked, about $0.0002 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
videodb
See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize…
lead-intelligence
AI-native lead intelligence and outreach pipeline. Replaces Apollo, Clay, and ZoomInfo with agent-powered signal scoring, mutual ranking, warm path discovery, and personalized outreach. Use when the user wants to find, qualify, and reach high-value contacts.
springboot-verification
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
team-builder
Interactive agent picker for composing and dispatching parallel teams.
cmd_aside
Answer a quick side question without interrupting or losing context from the current task. Resume work automatically after answering.
seo
Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.