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/cpliakas/claude-code-engineering-leaders/agents-mdgit clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/agents-md)<a href="https://agentmods.dev/instructions/cpliakas/claude-code-engineering-leaders/agents-md"><img src="https://agentmods.dev/badge/instructions/cpliakas/claude-code-engineering-leaders/agents-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.00713 | $0.00713 |
| Opus 5 | $0.00357 | $0.00357 |
| Sonnet 5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade C, and why
claude-code-engineering-leaders AGENTS.md scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf directory # NOT: rm -r directory How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI agents working in this repository.
Project Overview
engineering-leaders is a Claude Code plugin providing a virtual engineering
leadership team. It ships eight leadership agents (Chief Architect, Product
Owner, UX Strategist, Agile Coach, DevOps Lead, Engineering Manager, QA Lead,
Tech Lead) and fifteen skills covering the full SDLC: requirement refinement,
story/epic/ADR/runbook authoring, retrospectives, postmortems, and more.
The plugin is installed into other projects. Development work happens here; consumer projects install it from the marketplace or a local path.
Repository Layout
agents/ One .md file per agent (frontmatter + body)
skills/ One subdirectory per skill, each containing SKILL.md
hooks/ Plugin-level Claude Code hooks
tests/ Manual test scenarios (scenarios.md)
Authoring Conventions
Full conventions are documented in CLAUDE.md. Key rules for agents:
Agents (agents/<name>.md)
- Frontmatter fields:
name,description,model,color,memory: project descriptionmust include trigger phrases and delegation relationships- Names use kebab-case; colors are fixed per role (see
CLAUDE.md) - Body sections: Jurisdiction, Delegation, Key Knowledge, Memory Protocol
Skills (skills/<name>/SKILL.md)
- Frontmatter:
name,description, and optionallycontext: fork - Use
$ARGUMENTSfor parameterization - Use
context: forkfor skills that produce heavy output - Data files for a skill live in subdirectories of its skill directory
Agent vs. Skill
- Needs to learn and decide over time → agent
- Executes a fixed procedure → skill
- Agents invoke skills with
/skill-name; skills do not invoke agents
Onboarding model
/onboard— shared project context, writes to.claude/agent-memory/engineering-leaders/PROJECT.md/onboard-<agent>— per-agent context on top of the shared layer
Testing
Tests are manual scenarios in tests/scenarios.md. To run them:
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 · 93 lines · 713 tokens per session scan C 3cc4794b2d58
claude-code-engineering-leaders AGENTS.md is an instructions file published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 12d ago), licensed MIT. It adds 713 tokens to every session, about $0.0036 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.