Borrowing it
Nothing to install: this file belongs to paullukic/coograph. 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/paullukic/coograph/main/CLAUDE.mdgit clone --depth 1 https://github.com/paullukic/coographWrote 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/paullukic/coograph/claude-md)<a href="https://agentmods.dev/instructions/paullukic/coograph/claude-md"><img src="https://agentmods.dev/badge/instructions/paullukic/coograph/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.02291 | $0.02291 |
| Opus 5 | $0.01145 | $0.01145 |
| Sonnet 5 | $0.00458 | $0.00458 |
| Haiku 4.5 | $0.00229 | $0.00229 |
Grade A, and why
coograph 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 6d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Instructions
🛑 HARD RULE — CODE-GRAPH FIRST. Before any codebase search, navigation, tracing, or exploration you MUST use the code-graph MCP tools first (
mcp__code-graph__*). Only fall back tosqlite3 .code-graph/graph.db, and only then toGlob/Grep/Read, if the code-graph DB is genuinely NOT present in the workspace. Convenience is not a valid reason to skip. See "Tool Preferences" below.
🛑 HARD RULE — OPENSPEC OR STOP. For any change that modifies 2+ files, touches a spec, alters a public interface, or adds new behavior, you MUST create an OpenSpec in
openspec/changes/<date>-<slug>/and WAIT for user approval BEFORE writing code. Exemptions are narrow and literal:
- Typo fix in a single file
- Comment/docstring-only edit
- Config-value bump the user explicitly dictates (e.g., "set X=2")
- Follow-up fix for an already-approved, in-progress OpenSpec
"Trivial," "obvious," "I already know what to do," "small," and "just one tweak" are NOT exemptions. If in doubt → propose, don't code. See § Implementation Workflow for the full Plan → Propose → Apply flow.
Pre-flight (run on every session start)
Before doing any work, execute this checklist:
- Code-graph availability — call
get_minimal_contextwith a summary of the task. If it succeeds, code-graph is available and MUST be used for all navigation this session. If it fails, note that code-graph is unavailable and grep/glob fallback is permitted for this session. - Read conventions — read
.github/copilot-instructions.md(if not already loaded by the system). - Check in-progress work — look for open OpenSpecs in
openspec/changes/(skiparchive/). If one exists, summarize its status before starting new work. - OpenSpec gate — does this task already have an OpenSpec? If NO and it does not fit the exemption list in the HARD RULE above → STOP. Create the OpenSpec (
proposal.md,specs/<capability>/spec.md,tasks.md) and wait for approval before any code 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.
- 6d ago First seen · 146 lines · 2,291 tokens per session scan A fc8166870769
coograph CLAUDE.md is an instructions file published in the GitHub repository paullukic/coograph (17 stars, last pushed 1mo ago), licensed MIT. It adds 2,291 tokens to every session, about $0.0115 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
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.