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/captainme-ai/lead-dev-os/claude-mdgit clone --depth 1 https://github.com/CaptainMe-AI/lead-dev-osWrote 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/captainme-ai/lead-dev-os/claude-md)<a href="https://agentmods.dev/instructions/captainme-ai/lead-dev-os/claude-md"><img src="https://agentmods.dev/badge/instructions/captainme-ai/lead-dev-os/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.01706 | $0.01706 |
| Opus 5 | $0.00853 | $0.00853 |
| Sonnet 5 | $0.00341 | $0.00341 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
lead-dev-os 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 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.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Dev instructions for the lead-dev-os repository itself.
Project
lead-dev-os is a Claude Code plugin — a spec & context-driven framework for Claude Code development on large projects. It provides structured skills for product planning, spec writing, task scoping, and context-aware implementation.
The plugin lives in the lead-dev-os/ subdirectory. Everything outside that directory is repository-level supporting infrastructure (tests, docs, legacy code) and is not part of the distributed plugin.
License
MIT License
Terminology
- plugin — the
lead-dev-os/directory; this is what users point--plugin-dirat or install via a marketplace - target project — the project where the
lead-dev-osplugin is installed/enabled - spec — a feature specification (created in the target project)
- task — a scoped unit of work to be executed by the AI agent
- skill — a directory under
lead-dev-os/skills/containing aSKILL.mdfile; invoked as/lead-dev-os:<skill-name>
Plugin Architecture
This project follows the Claude Code plugin structure:
- Manifest:
lead-dev-os/.claude-plugin/plugin.json— defines plugin metadata (name,version,description,author, etc.). Thenamefield (lead-dev-os) is the namespace prefix for all skills. - Skills:
lead-dev-os/skills/— flat directory of skill folders, each containing aSKILL.mdentrypoint. Skills may include supporting files (templates, examples, scripts) alongsideSKILL.md. Claude Code auto-discovers skills from this directory. - Marketplace:
.claude-plugin/marketplace.jsonat the repository root — thecaptainme-aimarketplace catalog listing the plugin with a relative-path source ("./lead-dev-os"). This must live at the repo root (not inside the plugin) so/plugin marketplace add CaptainMe-AI/lead-dev-osfinds it. See Plugin marketplaces. - Inside the plugin, only
plugin.jsongoes inlead-dev-os/.claude-plugin/. All other directories (skills/, etc.) are at the plugin root level. Never putmarketplace.jsonthere — it would make Claude Code treat the plugin directory as a marketplace.
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 · 122 lines · 1,706 tokens per session scan A 05d5cd8fb11c
lead-dev-os CLAUDE.md is an instructions file published in the GitHub repository CaptainMe-AI/lead-dev-os (2 stars, last pushed 14d ago), licensed MIT. It adds 1,706 tokens to every session, about $0.0085 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
hydraflow CLAUDE.md
Claude Code instructions for T-rav/hydraflow, covering claude.md, quick rules (always apply), knowledge lookup, wiki topic index and workflow skills (adr-0044 p8/p10).
team-of-agents CLAUDE.md
Instructions for pranav8494/team-of-agents, covering claude.md, project rules for ai assistants and git commits.
gaia-skill-heaven CLAUDE.md
Claude Code instructions for gaia-research/gaia-skill-heaven, covering claude.md — gaia-skill-heaven, what this is, layout, commands and rule 0 — lifted (owner ruling, 2026-08-19).
foundry-research CLAUDE.md
Instructions for foundry-works/foundry-research, covering foundry research, plugin development, plugin gotchas and design principles.
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.