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/protomated/protomated-plugins-official/claude-mdgit clone --depth 1 https://github.com/protomated/protomated-plugins-officialWrote 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/protomated/protomated-plugins-official/claude-md)<a href="https://agentmods.dev/instructions/protomated/protomated-plugins-official/claude-md"><img src="https://agentmods.dev/badge/instructions/protomated/protomated-plugins-official/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.02753 | $0.02753 |
| Opus 5 | $0.01376 | $0.01376 |
| Sonnet 5 | $0.00551 | $0.00551 |
| Haiku 4.5 | $0.00275 | $0.00275 |
Grade B, and why
protomated-plugins-official 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 3d 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 MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
- The root `.mcp.json` is a local development MCP config (unrelated to the plugins) and must not contain committed credentials — keep tokens in env vars or gitignore the file. How it starts
The opening of the file, as written. The whole thing — 151 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.
What this repo is
A Claude plugin marketplace for solo attorneys, modeled on anthropics/claude-for-legal. It ships one flagship bundle (the Solo Attorney Starter Kit — eight skills), five of those eight skills as standalone plugins, the Legal Billing Tracker (a separate product with its own remote MCP server), and four further standalone, single-skill, connector-free plugins (Demand Letter Drafter, Estate Planning Document Assembler, Immigration Filing Drafter, Contract Document Reviewer) that each mirror their own upstream product repo. There is no runtime code for the drafting skills, no bundled MCP server, and no backend beyond the Legal Billing Tracker's own hosted service. The product is mostly content: markdown skill files, JSON manifests, and a Next.js landing page.
Repo layout
.claude-plugin/marketplace.json Marketplace manifest — every installable plugin, in curated order
solo-attorney-starter-kit/ Flagship bundle (all eight skills; also packaged into the release .zip)
.claude-plugin/plugin.json Identity manifest (kebab-case name, semver version)
.mcp.json Declares gmail + google-calendar + filesystem connectors
prompts/system-prompt.md Master system prompt — ethical guardrails live here
skills/*/SKILL.md One directory per skill; YAML frontmatter + markdown body
new-matter-organizer/ Standalone plugins — one skill each, same layout:
engagement-letter-drafter/ .claude-plugin/plugin.json, .mcp.json, README.md,
court-deadline-calendar/ skills/<skill-name>/SKILL.md
billing-narrative-drafter/
meeting-prep-brief/
legal-billing-tracker/ Standalone plugin (plugin.json name: legal-billing) — a
separate product, not split from the starter kit. Uses a
hosted remote MCP server instead of blank-url connectors.
demand-letter-drafter/ Standalone, connector-free plugins — one skill each,
estate-planning-document-assembler/ each mirroring its own upstream product repo.
immigration-filing-drafter/ .mcp.json is a committed empty `{}` (not generated by
contract-document-reviewer/ write-mcp-configs.mjs): these skills read only a
workspace folder the attorney explicitly attaches —
no MCP connector or auth step.
site/ Next.js landing page (Cloudflare Pages)
app/api/subscribe/route.ts Edge route: email capture → Kit API
scripts/
validate-plugin.mjs Validates marketplace.json + every listed plugin
write-mcp-configs.mjs Regenerates each plugin's .mcp.json (source of truth for connectors)
release-check.mjs Preflight for `npm run release`
docs/ Technical spec + planned-plugins.json (unbuilt catalog entries)
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.
- 3d ago First seen · 151 lines · 2,753 tokens per session scan B 82923187e2b5
protomated-plugins-official CLAUDE.md is an instructions file published in the GitHub repository protomated/protomated-plugins-official (2 stars, last pushed 24d ago), licensed Apache-2.0. It adds 2,753 tokens to every session, about $0.0138 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). 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.
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.