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/jontsai/claude-plugins/claude-mdgit clone --depth 1 https://github.com/jontsai/claude-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/jontsai/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/jontsai/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/jontsai/claude-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.00176 | $0.00176 |
| Opus 5 | $0.00088 | $0.00088 |
| Sonnet 5 | $0.00035 | $0.00035 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
claude-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 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.
What it actually says
Claude Code Instructions
This file provides guidance for Claude Code when working on this repository.
Quick Reference
- AGENTS.md - Technical guidelines for LLMs working on this codebase
- CONTRIBUTING.md - Contribution workflow and standards
- TESTING.md - How to validate and test plugins
Before Making Changes
- Read AGENTS.md for structural constraints
- Run
./scripts/validate.shafter changes - Follow patterns in existing plugins
Key Commands
# Validate everything
./scripts/validate.sh
# Test plugin install
/plugin marketplace add jontsai/claude-plugins
/plugin install researcher@jontsai
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 · 27 lines · 176 tokens per session scan A fa4d005b806a
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository jontsai/claude-plugins (6 stars, last pushed 23d ago), licensed MIT. It adds 176 tokens to every session, about $0.0009 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
claude-code-rules CLAUDE.md
Instructions for NikiforovAll/claude-code-rules, covering claude.md, repository overview, repo structure, website and important.
ccx-context-system CLAUDE.md
Claude Code instructions for shck-dev/ccx-context-system, covering claude.md, what this is, commands, architecture and load-bearing seams.
archeyes CLAUDE.md
Instructions for thisAAY/archeyes, covering archeyes — project guide, layout, design system, commands and publishing a release.
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.