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 agentmods add skills/anentrypoint/freddie/rfc-writernpx skills add AnEntrypoint/freddie --skill rfc-writergit clone --depth 1 https://github.com/AnEntrypoint/freddieWrote 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/anentrypoint/freddie/rfc-writer)<a href="https://agentmods.dev/skills/anentrypoint/freddie/rfc-writer"><img src="https://agentmods.dev/badge/skills/anentrypoint/freddie/rfc-writer.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00444 |
| Opus 5 | $0.00010 | $0.00222 |
| Sonnet 5 | $0.00004 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
rfc-writer 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 5d 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.
What it actually says
RFC Writer
Write clear, well-structured technical RFCs that drive decisions, not just describe ideas.
RFC structure
# RFC-NNN: <Title>
**Status**: Draft | In Review | Accepted | Rejected | Superseded by RFC-NNN
**Author(s)**: <names>
**Date**: YYYY-MM-DD
**Decision deadline**: YYYY-MM-DD
## Summary
One paragraph. What are we proposing, and why does it matter?
## Problem statement
Current situation, pain caused, data (error rates, latency, support tickets, developer hours).
## Goals
Specific, measurable outcomes this RFC achieves.
## Non-goals
Explicitly out of scope.
## Proposed solution
Architecture diagram (Mermaid preferred), key data structures, API contracts,
migration path, rollout plan (feature flags, gradual rollout, kill switch).
## Alternatives considered
For each: what it is, why rejected (specific reasons — not just "too complex").
## Impact assessment
| Dimension | Assessment |
|---|---|
| Performance | adds 2ms p99 latency |
| Security | no new attack surface |
| Reliability | one new external dependency |
| Cost | +$200/mo Snowflake compute |
## Open questions
Numbered list. Each has an owner and resolution deadline.
## Implementation plan
- [ ] Phase 1: ... (owner, ETA)
- [ ] Phase 2: ... (owner, ETA)
## References
Related RFCs, ADRs, tickets, papers, external docs.
Rules
- Problem statement before solution. Never lead with "we want to build X".
- Every alternative must explain specifically why it was rejected.
- Open questions must have owners. Ownerless questions are abandoned questions.
- Summary readable by someone unfamiliar with the domain.
- Total RFC under 2000 words. Appendices OK for data.
- If the decision deadline is missing, add one.
Describe the problem and rough solution and I will draft the RFC immediately.
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.
- 5d ago First seen · 69 lines · 19 tokens per session scan A deec099d154e
rfc-writer is a skill published in the GitHub repository AnEntrypoint/freddie (0 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 444 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-31.
Other skills, from other repositories
arch-save
Save an architect's state, clear its context, and re-init automatically — the packaged save→clear→re-init refresh cycle. Use when the owner directs a context refresh, or says "/arch-save", "save and clear", "refresh your context". Runs on the owner's direction; an architect does not invoke it autonomously mid-task.…
arch-init
Adopt an architect identity and recover its state from codev/state/ .md. Use when an architect terminal needs to (re)establish which architect it is — after a restart, context loss, or session handoff — or when the user says "/arch-init", "you are the X architect", or "recover your architect state". Identity resolves…
runnable-worktrees
Make builder worktrees runnable — the .codev/config.json worktree block (symlinks, postSpawn, devCommand), the afx dev CLI, VSCode dev controls, and per-stack config recipes. Use when configuring a repo so reviewers can run a builder's branch, when afx dev fails to bind or start, when a dev process is orphaned holding…
itchio-new-game-hunt
Hunt for fresh browser-playable games on itch.io /newest that are worth building SEO arbitrage sites for. Crawls new releases, scores them by signals, produces ranked shortlist.
codev
Codev project management CLI — init, adopt, update, and doctor commands. Check this skill before running any codev command (except consult, porch, or afx which have their own skills). Use when setting up new projects, adding codev to existing repos, updating framework files, or diagnosing missing dependencies.
porch
Protocol orchestrator CLI — drives SPIR, ASPIR, AIR, TICK, and BUGFIX protocols via a state machine. ALWAYS check this skill before running any porch command. Use when you need to check project status, approve gates, signal phase completion, or manage protocol state. Also use when a builder asks about gate approvals…