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/jpoutrin/product-forge/list-rfcsnpx skills add jpoutrin/product-forge --skill list-rfcsgit clone --depth 1 https://github.com/jpoutrin/product-forgeWrote 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/jpoutrin/product-forge/list-rfcs)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/list-rfcs"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/list-rfcs.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.00000 | $0.00935 |
| Opus 5 | $0.00000 | $0.00467 |
| Sonnet 5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
list-rfcs 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
list-rfcs
Category: Technical Architecture
Usage
/list-rfcs [options]
Options
| Option | Description |
|---|---|
--status <status> |
Filter by status (DRAFT, REVIEW, APPROVED, IN_PROGRESS, COMPLETED) |
--all |
Include archived RFCs |
--author <name> |
Filter by author |
| `--format table | list` |
Execution Instructions
When this command is run, Claude Code should:
-
Scan RFC Directories
rfcs/ ├── draft/ → DRAFT ├── review/ → REVIEW ├── approved/ → APPROVED │ └── in-progress/ → IN_PROGRESS ├── completed/ → COMPLETED └── archive/ → (only with --all) -
Extract Metadata from Each RFC
- RFC ID (from filename or frontmatter)
- Title
- Status
- Author
- Created date
- Last updated date
- Reviewers and their status
-
Apply Filters (if specified)
- Filter by status
- Filter by author
- Exclude archive unless
--all
-
Display Results
Table Format (default)
RFC Management Summary
======================
Active RFCs: 5 | In Review: 2 | Completed: 12
| RFC ID | Title | Status | Author | Updated |
|-----------|----------------------------|-------------|-----------|------------|
| RFC-0045 | API Gateway Selection | REVIEW | Jane Doe | 2025-12-05 |
| RFC-0044 | Cache Strategy | IN_PROGRESS | John Doe | 2025-12-04 |
| RFC-0043 | Auth Redesign | APPROVED | Jane Doe | 2025-12-01 |
| RFC-0042 | Database Migration | DRAFT | Bob Smith | 2025-11-28 |
| RFC-0041 | Logging Architecture | DRAFT | Jane Doe | 2025-11-25 |
Use '/rfc-status RFC-XXXX' to see details or update status.
List Format
RFC-0045: API Gateway Selection
Status: REVIEW
Author: Jane Doe
Created: 2025-12-01
Updated: 2025-12-05
Reviewers: Alice (approved), Bob (pending)
Location: rfcs/review/RFC-0045-api-gateway-selection.md
RFC-0044: Cache Strategy
Status: IN_PROGRESS
Author: John Doe
...
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 · 154 lines · 0 tokens per session scan A 8213fb0ca53b
list-rfcs is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 935 tokens. 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…