Borrowing it
Nothing to install: this file belongs to ensp1re/namescope. 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/ensp1re/namescope/main/CLAUDE.mdgit clone --depth 1 https://github.com/ensp1re/namescopeWrote 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/ensp1re/namescope/claude-md)<a href="https://agentmods.dev/instructions/ensp1re/namescope/claude-md"><img src="https://agentmods.dev/badge/instructions/ensp1re/namescope/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.00235 | $0.00235 |
| Opus 5 | $0.00118 | $0.00118 |
| Sonnet 5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
namescope 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.
This is a copy
86% identical to namescope AGENTS.md — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Shared Aiviron environment
This repository uses the project harness in .ai/. Claude must operate that harness automatically; the user should only need to describe work normally. Read .ai/README.md before repository-changing work.
If an active task exists, resume it when it matches the user's request, then compile its context for claude. For a new repository-changing request, internally create the task with objective and acceptance criteria, record a focused plan, and compile context before inspecting implementation files.
Treat compiled context as a closed scope. Inspect and edit only listed repository files. Expand deliberately with npx aiviron context add --file <path> --reason <why> before using another file. Before completion or handoff, check scope, run relevant verification, and persist criteria, plan progress, evidence, decisions, failures, and next actions.
For documentation tasks, use aiviron docs plan|init|check and context purpose document. Replace authoring prompts with verified knowledge and preserve human-owned docs. Never persist private reasoning, transcripts, authentication, or permissions.
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 · 12 lines · 235 tokens per session scan A 894f9de09efc
namescope CLAUDE.md is an instructions file published in the GitHub repository ensp1re/namescope (0 stars, last pushed 28d ago), licensed MIT. It adds 235 tokens to every session, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to namescope AGENTS.md, differing in 4 lines, and is treated as a copy.
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.