Borrowing it
Nothing to install: this file belongs to Aibier/claude-em-toolkit. 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/Aibier/claude-em-toolkit/main/CLAUDE.mdgit clone --depth 1 https://github.com/Aibier/claude-em-toolkitWrote 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/aibier/claude-em-toolkit/claude-md)<a href="https://agentmods.dev/instructions/aibier/claude-em-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/aibier/claude-em-toolkit/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/aibier/claude-em-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/aibier/claude-em-toolkit/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00571 | $0.00571 |
| Opus 5.5 | $0.00228 | $0.00228 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade B, and why
claude-em-toolkit 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 2mo 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 agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Default model is set in [`.claude/settings.json`](./.claude/settings.json). Don't switch to a heavier model mid task unless the task genuinely needs deeper reasoning (architecture decisions, ambiguous debugging). Routi How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Rules for Claude Code
These rules apply to all work in this repository. They're written as a reusable template — copy into your own project and adjust.
Commits & branches
- Use Conventional Commits style:
feat:,fix:,refactor:,docs:,test:,chore:. - Never commit directly to
main. Create a feature branch per change. - Never use
git push --force,git reset --hard, or skip hooks (--no-verify) without asking first. - Only create commits when the user explicitly asks.
Code style
- Match the existing formatting/linting config in the repo (don't introduce a new style).
- Prefer editing existing files over creating new ones.
- No speculative abstractions — solve the problem in front of you, not hypothetical future ones.
- Default to no comments; add one only when the why isn't obvious from the code.
Testing
- Every bug fix needs a regression test before it's considered done.
- Run the existing test suite before declaring a task complete; report failures honestly.
Ask before
- Installing/removing dependencies
- Modifying CI/CD config
- Any destructive or hard-to-reverse git operation
- Pushing to a shared remote
Cost and token efficiency
- Default model is set in
.claude/settings.json. Don't switch to a heavier model mid task unless the task genuinely needs deeper reasoning (architecture decisions, ambiguous debugging). Routine tasks (standup notes, formatting, simple lookups) run fine on lighter/faster models. - Read only the files and line ranges you actually need. Don't read whole large files when a
grepfor the relevant symbol would do. - For broad, multi area searches, dispatch scoped subagents (see
triage-researcher) rather than one sprawling search that fills your own context with raw output. - Don't re read files you just wrote or edited to "verify." A successful Edit/Write means the change landed; trust it.
- Prefer the permission allow list in
settings.jsonfor routine, safe commands (git log, git diff, tests) so you aren't re prompted on every run. Keep the deny list for destructive operations. - Schedule recurring routines (pulses, summaries, doc syncs) instead of running them ad hoc. A scheduled job that filters for "nothing notable, skip posting" (see
jira-progress-pulse) costs far less over a month than manually re running the same broad query.
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.
- 2mo ago First seen · 39 lines · 571 tokens per session scan B 1fee61c84e3d
claude-em-toolkit CLAUDE.md is an instructions file published in the GitHub repository Aibier/claude-em-toolkit (5 stars, last pushed 5mo ago), licensed MIT. It adds 571 tokens to every session, about $0.0023 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.