Borrowing it
Nothing to install: this file belongs to zgbrenner/agentcounsel. 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/zgbrenner/agentcounsel/main/CLAUDE.mdgit clone --depth 1 https://github.com/zgbrenner/agentcounselWrote 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/zgbrenner/agentcounsel/claude-md)<a href="https://agentmods.dev/instructions/zgbrenner/agentcounsel/claude-md"><img src="https://agentmods.dev/badge/instructions/zgbrenner/agentcounsel/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.00786 | $0.00786 |
| Opus 5 | $0.00393 | $0.00393 |
| Sonnet 5 | $0.00157 | $0.00157 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
agentcounsel 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 7d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — AgentCounsel
Claude Code's operating guide for this repository. The universal, tool-agnostic
operating manual is AGENTS.md; it is imported below, so every Claude Code
session loads it. Read it — everything in it applies. This file adds only what
is specific to Claude Code.
@AGENTS.md
Before anything else
- Decide your job: using a skill or editing the library (see
AGENTS.md). Never edit files underskills/,core/, oradapters/unless the task is explicitly to change the library. - Reload
core/every session. For any legal task, read every file incore/before reasoning about a skill. Claude does not retain them between sessions — treat each session as a fresh start and load the rules again.
Routing efficiently
- To find the right skill, prefer the index files —
WORKFLOW_ROUTER.md,SKILLS_INDEX.md,COMMANDS.md— over broad codebase searches. - When a task could span several skills and you need to scan many
SKILL.mdfiles, use the Explore subagent so the routing search does not flood the main context. Then open only the single narrowest skill. Loading unrelated practice areas degrades the work — see the LLM-pitfalls table inAGENTS.md. - Make independent reads in parallel: gather the
core/files and the chosenSKILL.mdin one batch.
Editing the library with Claude Code
When the task is explicitly to change the library:
- Use Plan mode for anything touching more than one skill,
core/, or a shared reference file — agree the plan before editing. - After your edits, before reporting done, run the validation suite from
AGENTS.md("Done means validation passes") and read the output. - Claude Code's
/reviewand/security-reviewcommands are useful here: run/reviewbefore opening a pull request, and/security-reviewfor any change that adds tooling or touchesscripts/. - Keep changes small and reviewable. A 12-line diff a maintainer can verify
beats a 600-line one they cannot — the generation–verification loop from
AGENTS.md, applied to library edits.
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.
- 7d ago First seen · 67 lines · 786 tokens per session scan A 47b3a32a1534
agentcounsel CLAUDE.md is an instructions file published in the GitHub repository zgbrenner/agentcounsel (18 stars, last pushed 1mo ago), licensed MIT. It adds 786 tokens to every session, about $0.0039 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
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).
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).
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.