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/fledgeling-co/fledgeling-plugins/claude-mdgit clone --depth 1 https://github.com/fledgeling-co/fledgeling-pluginsWrote 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/fledgeling-co/fledgeling-plugins/claude-md)<a href="https://agentmods.dev/instructions/fledgeling-co/fledgeling-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/fledgeling-co/fledgeling-plugins/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 | $0.02424 | $0.02424 |
| Opus 5 | $0.01212 | $0.01212 |
| Sonnet 5 | $0.00485 | $0.00485 |
| Haiku 4.5 | $0.00242 | $0.00242 |
Grade A, and why
fledgeling-plugins 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 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code when working in this repository.
Adding or renaming a plugin — four places, one commit
A plugin is not "added" when its directory exists. It is added when it is
installable and discoverable, and that takes four separate registrations. Land
all of them in the same commit as the plugin itself: a plugin present in
plugins/ but absent from the README is invisible to everyone who did not build
it, and absent from marketplace.json it cannot be installed at all.
plugins/<name>/.claude-plugin/plugin.json—name,description,version,author. Thenamemust match the directory and the marketplace entry exactly..claude-plugin/marketplace.json— append topluginswithsource: "./plugins/<name>"and acategory. Keepnameandversionidentical toplugin.json; a mismatch installs the wrong thing or nothing.plugins/<name>/README.md— what it does, how to invoke it, and what it refuses to do. This is the page the root README links to.- The root
README.mdrow, in the## The skillssection.
The root README row has a shape, and it breaks quietly
Copy an existing block exactly. Each entry is four parts in this order, and the separator is load-bearing:
<br clear="left" />
<a href="plugins/<name>/README.md"><img src="plugins/<name>/assets/icon-256.png" align="left" width="110" alt="" /></a>
### [<name>](plugins/<name>/README.md)
One paragraph: what it does and what makes it different.
The icon is floated left at 110px, so every entry needs its own
<br clear="left" /> before it. Omit it and the new icon floats up beside the
previous entry's paragraph — the row is present in the source, renders as an
overlapping mess, and reads to a human as "my plugin isn't in the README". That
failure has happened; it is why this section exists.
Two things to verify before committing, because both fail silently:
plugins/<name>/assets/icon-256.pngexists — the README shows a broken image otherwise, and nothing warns you.git ls-files -s plugins/<name>/skills/*/scriptsshows mode100755for anything executable. A script committed 644 fails at runtime for everyone who installs it, though it works fine on the machine that wrote it.
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 · 181 lines · 2,424 tokens per session scan A bfc7a19d9b32
fledgeling-plugins CLAUDE.md is an instructions file published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed today), licensed MIT. It adds 2,424 tokens to every session, about $0.0121 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).
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.
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.
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).