A command that fetches an IETF RFC and adds it to an OCaml project with documentation citation templates. An RFC is a published technical specification, often defining how internet protocols work.

Use it to download an RFC by number into the spec directory, extract its key structure and terminology, and create OCamldoc references for the module or sections that implement it.

It keeps the project’s local specification copy and code documentation linked to the standard being implemented.

add-rfc — Command for Claude Code by avsm

Install

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.

Clone the repo

git clone --depth 1 https://github.com/avsm/ocaml-claude-marketplace

Made for: Claude Code.

Or install ocaml-dev, the plugin that ships this one along with the rest of its 21 skills, 5 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/avsm/ocaml-claude-marketplace/add-rfc/github.svg)](https://agentmods.dev/commands/avsm/ocaml-claude-marketplace/add-rfc)

Your own site

<a href="https://agentmods.dev/commands/avsm/ocaml-claude-marketplace/add-rfc"><img src="https://agentmods.dev/badge/commands/avsm/ocaml-claude-marketplace/add-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/avsm/ocaml-claude-marketplace/add-rfc"><img src="https://agentmods.dev/badge/commands/avsm/ocaml-claude-marketplace/add-rfc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 827 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00017	$0.00827
Opus 5	$0.00009	$0.00413
Sonnet 5	$0.00003	$0.00165
Haiku 4.5	$0.00002	$0.00083

Measured 7d ago against content hash c7e7c7f7ccc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

add-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 7d 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.

plugins/ocaml-dev/commands/add-rfc.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add RFC

This command fetches an IETF RFC specification and integrates it into the project.

Arguments

RFC number: $ARGUMENTS (required, e.g., "6265" for HTTP cookies)

Process

1. Fetch the RFC

Fetch from IETF in plain text format:

https://datatracker.ietf.org/doc/html/rfc<NUMBER>.txt

Important: Always use .txt extension, not .html.

2. Save to spec/ Directory

Create spec/ directory if it doesn't exist and save:

spec/rfc<NUMBER>.txt

3. Parse RFC Structure

Extract key information:

RFC title and abstract
Table of contents (sections)
Key terminology definitions
Related RFCs (obsoletes, updates, references)

4. Generate OCamldoc Citation Templates

Provide ready-to-use citations for:

Module-level:

(** RFC <NUMBER> <Title>.

    This module implements <description> as specified in
    {{:https://datatracker.ietf.org/doc/html/rfc<NUMBER>}RFC <NUMBER>}.

    {2 References}
    {ul
    {- {{:https://datatracker.ietf.org/doc/html/rfc<NUMBER>}RFC <NUMBER>} - <Title>}} *)

Section-specific:

(** Implements {{:https://datatracker.ietf.org/doc/html/rfc<NUMBER>#section-N}RFC <NUMBER> Section N}. *)

5. Suggest Integration Points

Search the codebase for:

Functions that might implement RFC sections
Existing RFC references that could be improved
Types that represent RFC concepts

Output

Provide:

Confirmation of RFC download
Summary of RFC contents (title, sections)
OCamldoc citation templates, worded under the doc-style skill
Suggestions for where to add citations in existing code

Example Usage

/add-rfc 6265
/add-rfc 3492

Success Output

Fetched RFC 6265: HTTP State Management Mechanism

Saved to: spec/rfc6265.txt

RFC Summary:
  Title: HTTP State Management Mechanism
  Obsoletes: RFC 2965
  Sections:
    1. Introduction
    2. Conventions
    3. Overview
    4. Server Requirements
    5. User Agent Requirements
    6. Implementation Considerations
    7. Privacy Considerations
    8. Security Considerations

OCamldoc Templates:

Module-level:
(** RFC 6265 HTTP State Management Mechanism.

    This module implements HTTP cookie handling as specified in
    {{:https://datatracker.ietf.org/doc/html/rfc6265}RFC 6265}. *)

Section references:
- {{:https://datatracker.ietf.org/doc/html/rfc6265#section-4}RFC 6265 Section 4} - Server Requirements
- {{:https://datatracker.ietf.org/doc/html/rfc6265#section-5}RFC 6265 Section 5} - User Agent Requirements
- {{:https://datatracker.ietf.org/doc/html/rfc6265#section-5.2}RFC 6265 Section 5.2} - The Set-Cookie Header

Related RFCs you might also need:
- RFC 2616 - HTTP/1.1 (obsoleted by RFC 7230-7235)
- RFC 7230 - HTTP/1.1 Message Syntax and Routing

Read the full file on GitHub · 121 lines

Changes

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.

7d ago Changed c7e7c7f7ccc8
11d ago First seen · 121 lines · 17 tokens per session scan A bcb4fadc44a2

Subscribe to this mod's changes

add-rfc is a command published in the GitHub repository avsm/ocaml-claude-marketplace (35 stars, last pushed 9d ago), licensed ISC. It adds 17 tokens to every session and 827 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-30.

Languages Research

fastapi

FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…

mfmezger/ai_agent_dotfiles · 84 tokens

add-rfc