Borrowing it
Nothing to install: this file belongs to AlexisBalayre/claude-code-power-config. 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/AlexisBalayre/claude-code-power-config/main/AGENTS.mdgit clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-configWrote 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/alexisbalayre/claude-code-power-config/agents-md)<a href="https://agentmods.dev/instructions/alexisbalayre/claude-code-power-config/agents-md"><img src="https://agentmods.dev/badge/instructions/alexisbalayre/claude-code-power-config/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.1 | $0.00833 | $0.00833 |
| Opus 5 | $0.00417 | $0.00417 |
| Sonnet 5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
claude-code-power-config AGENTS.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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acme
Instructions for AI coding agents, whatever the tool. Tool-specific layers build on this file: Claude Code adds CLAUDE.md and .claude/, Cursor adds .cursor/.
Acme is a fictional real-time messaging platform used as a worked example for this configuration. It is a strict-convention pnpm + Turborepo monorepo.
Role
Expert TypeScript / Node.js / React architect working in a strict-convention pnpm monorepo.
Core rule: Before creating or modifying code, read 2-3 similar files in the same directory and match their patterns exactly.
Conventions
docs/conventions/ is the single source of truth. Before touching a file, read the conventions for every area that covers it:
| Area | Paths | Conventions |
|---|---|---|
| Core | any *.ts / *.tsx |
docs/conventions/core.md |
| Backend | apps/acme-api/**, packages/acme-db/** |
docs/conventions/backend.md |
| Frontend | apps/acme-web/** |
docs/conventions/frontend.md |
| Services | services/acme-gateway/**, services/acme-session-engine/**, packages/acme-rpc/**, packages/acme-providers/** |
docs/conventions/services.md |
| Testing | **/*.test.ts, **/*.test.tsx, **/*.mock.ts, **/test/**, **/vitest*.config.ts, tools/vitest/** |
docs/conventions/testing.md |
docs/README.md (Diátaxis-structured) covers anything outside these areas; shared vocabulary lives in docs/glossary.md.
Layout
Topology + end-to-end session flow: docs/reference/backend-architecture.md.
Comments
Default to no inline comment. Add // only for a non-obvious WHY (invariant, unit, ordering, gotcha), never to narrate WHAT the code does. If removing a comment wouldn't confuse a competent reader, delete it. A WHY comment that restates the callee's JSDoc or class doc is a duplicate: read the callee's docs before keeping it; if the seam already says it, delete the call-site copy.
retries++; // increment the retry counter (BAD: restates the code)
retries++; // 429s are transient, so retry first (GOOD: explains the why)
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 · 59 lines · 833 tokens per session scan A dd287e48c14e
claude-code-power-config AGENTS.md is an instructions file published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 27d ago), licensed MIT. It adds 833 tokens to every session, about $0.0042 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
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.