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 instructions/mcrundo/franklin/claude-mdgit clone --depth 1 https://github.com/mcrundo/franklinWrote 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/instructions/mcrundo/franklin/claude-md)<a href="https://agentmods.dev/instructions/mcrundo/franklin/claude-md"><img src="https://agentmods.dev/badge/instructions/mcrundo/franklin/claude-md.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.1 | $0.00693 | $0.00693 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
franklin CLAUDE.md 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 6d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Franklin
Turns technical books (EPUB) into Claude Code plugins via a staged pipeline: ingest → map → plan → reduce → assemble.
Stack
- Python 3.12, managed with
uv - Typer CLI (
franklin), Pydantic v2 models, Rich output - Anthropic SDK for LLM calls, tenacity for retries
- ruff (line-length 99), mypy strict, pytest
Commands
uv sync # install
uv run franklin ingest BOOK # run ingest stage
uv run pytest # tests
uv run ruff check . # lint
uv run ruff format . # format
uv run mypy # type check
Run directories land in ./runs/<slug>/ — book.json plus raw/chNN.json per chapter. Ingest is deterministic, no LLM calls.
Layout
src/franklin/cli.py— Typer entrypoint; per-stage commands are thin shells over_do_<stage>_stagehelpers.src/franklin/services/— stage services (IngestService, MapService, PlanService, ReduceService, AssembleService). Each takes a Pydantic input, emits ProgressEvents via a callback, returns a Pydantic result. Independent of Typer/Rich — usable from non-CLI callers.src/franklin/ingest/,mapper/,planner/,reducer/,assembler/— stage-pure primitives (parsers, LLM callers, validators). Services orchestrate; these do the work.src/franklin/llm/— Anthropic client wrapper, prompt loader, prompts as markdown.src/franklin/schema.py— Pydantic schemas (BookManifest, ChapterSidecar, PlanManifest, Artifact, etc.) — the contract between stages.tests/— pytest.test_golden_path.pyis the end-to-end regression oracle that threads all five stages with a scripted fake Anthropic client.
Working preferences
- Use
uv runfor anything Python — never barepythonorpip. - Keep mypy strict-clean and ruff-clean before declaring a task done.
- Prefer editing existing files; don't create new modules speculatively.
- Prompts live as markdown under
src/franklin/llm/prompts/and are loaded by the prompt loader — add new ones there, don't inline strings. - Pydantic models are the contract between stages. When changing a stage's output, update the model first.
- Don't commit unless asked. When asked, write terse commit messages matching the existing log style (
Add X,Classify Y, imperative, no body unless needed).
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.
- 6d ago First seen · 48 lines · 693 tokens per session scan A f3ea64708d07
franklin CLAUDE.md is an instructions file published in the GitHub repository mcrundo/franklin (9 stars, last pushed 4mo ago), licensed MIT. It adds 693 tokens to every session, about $0.0035 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.