Borrowing it
Nothing to install: this file belongs to yal212/hangar.nvim. 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/yal212/hangar.nvim/main/CLAUDE.mdgit clone --depth 1 https://github.com/yal212/hangar.nvimWrote 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/yal212/hangar.nvim/claude-md)<a href="https://agentmods.dev/instructions/yal212/hangar.nvim/claude-md"><img src="https://agentmods.dev/badge/instructions/yal212/hangar.nvim/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.00304 | $0.00304 |
| Opus 5 | $0.00152 | $0.00152 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
hangar.nvim 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 5d 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.
What it actually says
CLAUDE.md
Project rules for AI assistants working in this repo. Everything in CONTRIBUTING.md applies too —
this file only covers what is specific to automated contributors.
Attribution
Agent-authored work is credited by a Co-Authored-By: trailer and nothing else.
- Never append a
Claude-Session:trailer — or anyhttps://claude.ai/code/session_…URL — to a commit message. Those links resolve only inside one person's local Claude Code install, so they are noise in a public history.scripts/hooks/commit-msgstrips them, but do not rely on the hook: do not write them in the first place. - Never append a
🤖 Generated with [Claude Code]footer, or a session URL, to a PR body, an issue, a comment, or a review. No hook can catch these — this rule is the only guard. Co-Authored-By: Claude <model> <[email protected]>is welcome and stays.
The history was rewritten once to remove these trailers. Do not reintroduce them.
Everything else
Read CONTRIBUTING.md: conventional-commit subjects, make check before pushing, a CHANGELOG.md
entry under [Unreleased] for user-facing changes, and doc/hangar.txt kept in step with the
README.
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.
- 5d ago First seen · 25 lines · 304 tokens per session scan A 55a1f2c78a76
hangar.nvim CLAUDE.md is an instructions file published in the GitHub repository yal212/hangar.nvim (1 stars, last pushed 10d ago), licensed MIT. It adds 304 tokens to every session, about $0.0015 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.