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/fradser/dotclaude/claude-mdgit clone --depth 1 https://github.com/FradSer/dotclaudeWrote 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/fradser/dotclaude/claude-md)<a href="https://agentmods.dev/instructions/fradser/dotclaude/claude-md"><img src="https://agentmods.dev/badge/instructions/fradser/dotclaude/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.01129 | $0.01129 |
| Opus 5 | $0.00564 | $0.00564 |
| Sonnet 5 | $0.00226 | $0.00226 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade A, and why
dotclaude 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repository Overview
This is a Claude Code plugin marketplace (frad-dotclaude) containing 21 plugins across development and productivity categories. Each plugin follows auto-discovery conventions—place components in commands/, agents/, skills/ directories and Claude discovers them automatically.
Active plugins: git, github, refactor, swiftui, office, lark, hyperframes, plugin-optimizer, mattpocock, superpowers, antigravity, pi, interfaces, storm, hardware, autoresearch, memory
Non-active plugins: acpx, code-context, utils, meeseeks-vetted
Plugin Structure
plugin-name/
├── .claude-plugin/plugin.json # Manifest with commands/agents/skills/hooks
├── agents/*.md # Agent definitions
├── skills/skill-name/ # Skill directories
│ ├── SKILL.md # Main skill file (required)
│ └── references/ # Detailed reference materials
├── scripts/ # Utility scripts (bash/python)
└── examples/ # Example configurations
Skill registration determines visibility. A skill registered under "commands" in plugin.json becomes a user-invocable slash command (e.g., /git:commit). A skill registered under "skills" is internal-only, loaded automatically when Claude needs domain knowledge but never shown in /help. Example from refactor/:
"commands": ["./skills/refactor/"]-- user runs/refactor:refactor"skills": ["./skills/best-practices/"]-- loaded automatically during refactoring
Hooks can be inline in plugin.json. See git/.claude-plugin/plugin.json for the PreToolUse hook pattern (runs a shell script to validate Bash tool calls before execution).
Development Workflow
Validation: Run /plugin-optimizer:optimize-plugin before committing. Alternatively:
# All checks (structure, manifest, frontmatter, tools, tokens)
python3 plugin-optimizer/scripts/validate-plugin.py <plugin-path>
# Specific checks only
python3 plugin-optimizer/scripts/validate-plugin.py <plugin-path> --check=manifest,frontmatter
# JSON output for scripting
python3 plugin-optimizer/scripts/validate-plugin.py <plugin-path> --json
# Verbose (shows passing checks too)
python3 plugin-optimizer/scripts/validate-plugin.py <plugin-path> -v
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.
- 4d ago First seen · 84 lines · 1,129 tokens per session scan A fc180d36360c
dotclaude CLAUDE.md is an instructions file published in the GitHub repository FradSer/dotclaude (588 stars, last pushed 23d ago), licensed MIT. It adds 1,129 tokens to every session, about $0.0056 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.
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.