Borrowing it
Nothing to install: this file belongs to yannlugrin/claude. 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/yannlugrin/claude/main/CLAUDE.mdgit clone --depth 1 https://github.com/yannlugrin/claudeWrote 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/yannlugrin/claude/claude-md)<a href="https://agentmods.dev/instructions/yannlugrin/claude/claude-md"><img src="https://agentmods.dev/badge/instructions/yannlugrin/claude/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.00799 | $0.00799 |
| Opus 5 | $0.00400 | $0.00400 |
| Sonnet 5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
claude 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this repository is
A personal collection of Claude Code assets — not an application; the deliverables are the asset files themselves. The toolchain is just over pre-commit: just setup creates .venv/ from the pinned requirements.txt and installs the git hook, just check [all|changed] runs every lint, just test runs this repository's own behaviour, just verify runs both. Checks live once in .pre-commit-config.yaml, so the git hook and just check cannot look for different things.
Structure
skills/— one directory per skill containing aSKILL.md(frontmatter needsdescription; the directory name is the skill/command name)skills/index-project/— the catalog's write path: run inside a project, it drafts that project's entry (role, status, family, relations) and writes it after approvalagents/— subagent definitions, one.mdper agent with frontmatter (name,description, optionallymodel,tools); thenamefield, not the filename, is the identityhooks/— hook scripts; symlinking alone does nothing, they must also be registered in asettings.jsonhooksblockhooks/project-catalog.py—SessionStarthook and CLI for the project catalog: injects one line per project (name, path, one-line role, last activity), andshow <name>reads that project's git state and README live. Its data lives in~/.claude/catalog/, never here —upsertrefuses any target inside this checkoutexamples/— scratch/reference material; git-ignored (it also contains a nested git repo — leave it alone)manage.py— enable/disable tool: symlinks assets into~/.claude/(or--target <dir>);status,enable/disablewith names or--allscripts/lint-assets.py— validates asset frontmatter (skills need adescription, agents needname+description); runs via pre-commit, whose hooks are defined in.pre-commit-config.yamland use the.venv/tools directly.claude/hooks/bash_guard.py— this repository's ownPreToolUseguard, registered in.claude/settings.json. Only itsREGISTRYsection is repository-specific; the engine above that banner is a copy of the template inskills/specify/references/handoff-assets/and is refreshed from it by hand. Add a rule and add aCASESentry:--selftestfails on a rule no case reaches
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 · 30 lines · 799 tokens per session scan A ee3ad18132b0
claude CLAUDE.md is an instructions file published in the GitHub repository yannlugrin/claude (2 stars, last pushed 10d ago), licensed MIT. It adds 799 tokens to every session, about $0.0040 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.