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/claude-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/claude-md)<a href="https://agentmods.dev/instructions/cpliakas/claude-code-engineering-leaders/claude-md"><img src="https://agentmods.dev/badge/instructions/cpliakas/claude-code-engineering-leaders/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.01004 | $0.01004 |
| Opus 5 | $0.00502 | $0.00502 |
| Sonnet 5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
claude-code-engineering-leaders 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 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.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
engineering-leaders
A Claude Code plugin providing engineering leadership agents — the virtual leadership team that refines requirements, sets technical direction, and governs delivery.
Authoring Conventions
Markdown Body
- Always add a blank line between a heading (or bold-text header like
**Triggers:**) and the following list or paragraph. Omitting the blank line violates MD022/MD032 and can cause rendering issues.
Agents
-
One markdown file per agent in
agents/ -
Follow the agent definition template: frontmatter (name, description, model, memory) + body (jurisdiction, delegation, key knowledge, memory protocol)
-
Descriptions must include trigger phrases AND delegation relationships
-
All agents use
memory: project— they learn per-project -
Agent names use kebab-case
-
Agent colors are assigned by role to ensure visual distinction in the Claude Code UI:
Agent Color Rationale chief-architect blue Strategic authority, long-term thinking product-owner yellow Planning and prioritization (sticky-note energy) ux-strategist magenta Creative, user-empathy, experience focus agile-coach green Process health, go/no-go signals devops-lead cyan Infrastructure, operational tooling engineering-manager orange Meta-observation, systemic feedback qa-lead red Quality gates, risk signals tech-lead purple Tactical orchestration, convention ownership
Skills
- One directory per skill in
skills/<skill-name>/ - Must contain
SKILL.mdwith YAML frontmatter - Skills are opinionated procedures with clear inputs, process steps, and outputs
- Use
$ARGUMENTSfor parameterization - Use
context: forkfor skills that produce a lot of output (keeps main context clean) - Skills can bundle data files in subdirectories — reference them via Glob/Read relative to the skill directory
Agent vs Skill Decision
- If it needs to learn and decide → agent
- If it needs to execute a procedure → skill
- Agents use skills; skills don't use agents
- Agents reference skills with the
/prefix (e.g.,/write-runbook) in their markdown — Claude invokes the skill autonomously when the agent's instructions call for it
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 · 95 lines · 1,004 tokens per session scan A 84a6f42340f7
claude-code-engineering-leaders CLAUDE.md is an instructions file published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 14d ago), licensed MIT. It adds 1,004 tokens to every session, about $0.0050 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
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 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.
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).