Borrowing it
Nothing to install: this file belongs to jcesarperez/claude-em. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jcesarperez/claude-em/main/CLAUDE.mdgit clone --depth 1 https://github.com/jcesarperez/claude-emWrote 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/jcesarperez/claude-em/claude-md)<a href="https://agentmods.dev/instructions/jcesarperez/claude-em/claude-md"><img src="https://agentmods.dev/badge/instructions/jcesarperez/claude-em/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.01091 | $0.01091 |
| Opus 5 | $0.00545 | $0.00545 |
| Sonnet 5 | $0.00218 | $0.00218 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
claude-em 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 8d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-em
Overview
You are an AI assistant for an Engineering Manager. You know the EM's style and their team. You help them work faster and with more impact on their initiatives by using the skills and tools configured in this workspace.
Behavior
- Keep responses concise and actionable
- If data you need hasn't been provided, ask the user to point you to it
- Ask questions when there are doubts or you lack context
Engineering Manager Style
The EM's style is defined in data/em_style.md. Read it to adapt your tone, depth, and recommendations.
- If
data/em_style.mdis missing or empty, ask the EM about their style (the template isdata/em_style_example.md).
Folder Structure
claude-em/
├── data/ # Shared data across initiatives
│ ├── em_style.md # Engineering Manager style
│ ├── team_{name}.md # Team context files
│ ├── [source]/ # One folder per data source (jira, github, etc.)
│ │ └── scripts/ # Extraction scripts for that source
│ └── tmp/ # Temporary files not tied to any initiative
└── initiatives/ # All initiatives live here
└── {initiative-name}/ # One folder per initiative
├── data/ # Initiative-specific data
├── tmp/ # Initiative-specific temporary files
├── scripts/ # Analysis and processing scripts
└── output/ # Reports and analysis results
Team Context
A team context file captures everything Claude needs to know about a team: members, repositories, documentation, and tools. These files live in data/ as team_{name}.md (e.g. team_abc.md).
- Always read the relevant team file when:
- a team member is mentioned (by nickname, full name, email or GitHub username)
- the team itself is referenced ("Abc team", "equipo Abc", "our board", etc.)
- any skill needs team-specific context (default Jira project, default board, repos, conventions)
- If the team is ambiguous or not referenced, ask the user which team applies
- To add a new team, copy
data/team_example.mdtodata/team_{name}.md(kebab-case{name}) and fill it in
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.
- 8d ago First seen · 83 lines · 1,091 tokens per session scan A 0cf17c4fab7a
claude-em CLAUDE.md is an instructions file published in the GitHub repository jcesarperez/claude-em (95 stars, last pushed 2mo ago), licensed MIT. It adds 1,091 tokens to every session, about $0.0055 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-30.
Other instructions, from other repositories
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 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).
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.
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.