Borrowing it
Nothing to install: this file belongs to agpalindrome/ferric-fred. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agpalindrome/ferric-fred/main/CLAUDE.mdgit clone --depth 1 https://github.com/agpalindrome/ferric-fredWrote 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/agpalindrome/ferric-fred/claude-md)<a href="https://agentmods.dev/instructions/agpalindrome/ferric-fred/claude-md"><img src="https://agentmods.dev/badge/instructions/agpalindrome/ferric-fred/claude-md/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/instructions/agpalindrome/ferric-fred/claude-md"><img src="https://agentmods.dev/badge/instructions/agpalindrome/ferric-fred/claude-md.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.01620 | $0.01620 |
| Opus 5 | $0.00810 | $0.00810 |
| Sonnet 5 | $0.00324 | $0.00324 |
| Haiku 4.5 | $0.00162 | $0.00162 |
Grade A, and why
ferric-fred 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 8d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ferric-fred — Claude Code guidance
Rust workspace: a strongly-typed FRED API client library, a CLI (ratatui TUI),
and an MCP server. See README.md and docs/adr/ for orientation.
These rules layer on top of the global permission model (auto mode + classifier). Their job is to tell the classifier what counts as "important" to delete or create in this repo — the global config only guards universal catastrophes.
Keep documentation current
Documentation is part of the change, not a follow-up. Before opening any PR, check whether it touches user-facing behaviour, the public API, or a design decision, and update the affected docs in the same PR. The doc surfaces here:
- Workspace
README.md— CLI usage examples, the MCP tool table, and the endpoint/status summary. Update when commands, flags, tools, or coverage change. - Per-crate
README.md(crates/*/README.md) — the crates.io / docs.rs landing pages; keep the install/usage/feature blurbs in step with reality. - Crate-level rustdoc (
//!in each crate'slib.rs/main.rs) plus item docs — the docs.rs front page; refresh when the surface or the story changes. - ADRs (
docs/adr/) — record a new ADR for any non-trivial design or process decision (see Deletion & creation for the append-only rule). - CLI
--help(clap doc comments) and MCP tool descriptions — these are the docs for those surfaces; a new flag or tool means new/updated help text. CONTRIBUTING.mdwhen the contribution workflow changes.
Rule of thumb: a new or changed endpoint touches the library docs + workspace README + MCP tool table; a new feature touches the relevant crate README(s) and crate-level rustdoc; a decision gets an ADR. If a change makes an existing doc wrong, fixing it is in scope for that PR — not a later one.
Repo settings are code
Repo-level GitHub settings (the Actions "create/approve PRs" toggle,
delete_branch_on_merge, merge methods, description, topics, …) are the source
of truth in scripts/repo-settings.sh, per
ADR-0022. Change them by editing that
script and running apply via a reviewed PR — not by hand in the GitHub UI, or
the drift-check (repo-settings.sh check) will flag it. Org-wide settings (branch
protection, rulesets) are not here — they live in ojhermann-org/github-settings.
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.
- 8d ago First seen · 115 lines · 1,620 tokens per session scan A dbe34dc0af10
ferric-fred CLAUDE.md is an instructions file published in the GitHub repository agpalindrome/ferric-fred (0 stars, last pushed 19d ago), licensed Apache-2.0. It adds 1,620 tokens to every session, about $0.0081 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
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.
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 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).
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).
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.
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.