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/crathgeb/claude-plugin-studio/claude-mdgit clone --depth 1 https://github.com/crathgeb/claude-plugin-studioWrote 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/crathgeb/claude-plugin-studio/claude-md)<a href="https://agentmods.dev/instructions/crathgeb/claude-plugin-studio/claude-md"><img src="https://agentmods.dev/badge/instructions/crathgeb/claude-plugin-studio/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.01017 | $0.01017 |
| Opus 5 | $0.00508 | $0.00508 |
| Sonnet 5 | $0.00203 | $0.00203 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade B, and why
claude-plugin-studio CLAUDE.md scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
│ └── settings.ts # Reads ~/.claude/settings.json How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Plugin Studio
Development tool for Claude Code plugins - watch, validate, and auto-sync during development.
Bash Commands
npm run build- Build the project with tsup (outputs to dist/)npm run dev- Build in watch mode for developmentnpm run test- Run tests in watch mode with Vitestnpm run test:run- Run tests oncenpm run typecheck- Type check without emittingnpm link- Link globally to usecpscommand
CLI Commands
cps- Start watching plugins/marketplaces (default action)cps watch- Explicit watch commandcps validate- One-time validation without watchingcps create- Interactively create a new marketplace or plugincps --verboseor-v- Run with detailed outputcps --quietor-q- Run with errors only
Code Style
- TypeScript with strict mode
- ESM modules (
"type": "module"in package.json) - Use
.jsextension in imports (e.g.,import { Scanner } from './scanner.js') - Interfaces over types for object shapes
- Explicit return types on exported functions
- Tests colocated with source files (
*.test.ts)
Architecture
src/
├── cli.ts # Entry point, commander setup
├── types.ts # Shared TypeScript interfaces
├── scanner.ts # Finds plugins/marketplaces recursively
├── watcher.ts # File watching with chokidar (300ms debounce)
├── scaffolder.ts # Creates plugin/marketplace scaffolding
├── commands/ # CLI command implementations
│ ├── watch.ts # Watch command logic
│ └── create.ts # Create command logic
├── templates/ # Template generators
│ └── index.ts # Generates manifests and sample skills
├── schemas/ # JSON schemas for validation
│ ├── plugin.schema.json
│ └── marketplace.schema.json
├── validator/ # Three-layer validation
│ ├── index.ts # Orchestrator (stops on first failure)
│ ├── schema.ts # JSON schema validation with ajv
│ ├── structure.ts # Checks referenced paths exist
│ └── claude-cli.ts # Wraps `claude plugin validate`
├── sync/ # Cache clearing and reinstallation
│ ├── index.ts # Orchestrator
│ ├── cache.ts # Manages ~/.claude/plugins/cache/
│ ├── installer.ts # Runs claude CLI commands
│ └── settings.ts # Reads ~/.claude/settings.json
└── ui/
├── logger.ts # Verbosity-aware logging with chalk
└── prompt.ts # Interactive selection with inquirer
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 · 105 lines · 1,017 tokens per session scan B 0dd7c1550918
claude-plugin-studio CLAUDE.md is an instructions file published in the GitHub repository crathgeb/claude-plugin-studio (2 stars, last pushed 7mo ago), licensed MIT. It adds 1,017 tokens to every session, about $0.0051 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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).
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.
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).
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.