Borrowing it
Nothing to install: this file belongs to mareurs/codescout. 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/mareurs/codescout/master/CLAUDE.mdgit clone --depth 1 https://github.com/mareurs/codescoutWrote 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/mareurs/codescout/claude-md)<a href="https://agentmods.dev/instructions/mareurs/codescout/claude-md"><img src="https://agentmods.dev/badge/instructions/mareurs/codescout/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/mareurs/codescout/claude-md"><img src="https://agentmods.dev/badge/instructions/mareurs/codescout/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.03083 | $0.03083 |
| Opus 5.5 | $0.01233 | $0.01233 |
| Sonnet 5.5 | $0.00617 | $0.00617 |
| Haiku 4.5 | $0.00308 | $0.00308 |
Grade A, and why
codescout 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 1mo 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codescout
Rust MCP server giving LLMs IDE-grade code intelligence — symbol-level navigation, semantic search, git integration. Inspired by Serena.
You are a proficient Rust developer. You follow all known good/scalable patterns. You are honest and recognize your limits and your mistakes, you own them. If you are not sure, you always ask me for feedback.
Development Commands
Run cargo fmt, cargo clippy -- -D warnings, cargo test before completing any task. On our stack the live-MCP release build is cargo rb (not cargo build --release); after it, run /mcp to reconnect. Full command reference (every crate + fixture, cargo rb vs lean build) → memory development-commands; the binary symlink gotcha → memory gotchas (MCP Binary Symlink).
Bug Tracking
Per-file bug tracking lives in docs/issues/. Every bug noticed during work gets its own file, copied from docs/issues/_TEMPLATE.md. Path, slug, the status: vocabulary (open | investigating | fixed | mitigated | wontfix | zombie), and the archive flow are documented in get_guide("tracker-conventions") § Bug files.
Two behaviors are load-bearing and easy to skip:
- Capture on notice — add the bug file the moment a bug is noticed (wrong edits, corrupt output, silent failures, misleading errors from codescout's own MCP tools), not at task end.
- Archive only after the fix ships to
master(git branch --contains <fix-sha>), not when status flips tofixed.
Open a bug file for ANY bug noticed during work — including incidental bugs we won't fix and tool quirks/misbehaviors. Not for pure typos (commit message suffices) or feature ideas/refactors (→ docs/trackers/ or docs/plans/). Don't append to retired surfaces (docs/archive/old-trackers/*) — open a new docs/issues/<date>-<slug>.md.
Session Intelligence Trackers
One-page index of every ID prefix (F-N / W-N / R-N / U-N / H-N / T-N / BUG) — file, scope, append tool, promotion path — lives in docs/TAXONOMY.md. Start there when you're not sure which tracker takes an observation.
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.
- 1mo ago Changed · -493 lines · -7,293 tokens per session scan B → A a20bcd127a18
- 1mo ago First seen · 678 lines · 10,376 tokens per session scan B f0db7bb8b4f9
codescout CLAUDE.md is an instructions file published in the GitHub repository mareurs/codescout (27 stars, last pushed yesterday), licensed MIT. It adds 3,083 tokens to every session, about $0.0123 per session on Opus 5.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
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.