Borrowing it
Nothing to install: this file belongs to rixinhahaha/snip. 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/rixinhahaha/snip/main/CLAUDE.mdgit clone --depth 1 https://github.com/rixinhahaha/snipWrote 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/rixinhahaha/snip/claude-md)<a href="https://agentmods.dev/instructions/rixinhahaha/snip/claude-md"><img src="https://agentmods.dev/badge/instructions/rixinhahaha/snip/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.02006 | $0.02006 |
| Opus 5 | $0.01003 | $0.01003 |
| Sonnet 5 | $0.00401 | $0.00401 |
| Haiku 4.5 | $0.00201 | $0.00201 |
Grade A, and why
snip 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Autonomous Agent Instructions
This project is fully autonomous. Claude Code operates independently across all roles: product, design, development, DevOps. Read the relevant role docs before making changes.
Role Documents
| Doc | When to Read |
|---|---|
docs/PRODUCT.md |
Before adding features, changing UX, or making product decisions. Contains vision, terminology, and product principles. |
docs/DESIGN.md |
Before touching CSS, colors, or UI components. Contains the full color system (Dark/Light), component patterns, and glass effect specs. |
docs/ARCHITECTURE.md |
Before writing code. Contains directory structure, code conventions, IPC channels, data flow, and key architectural constraints. |
docs/DEVOPS.md |
Before changing build scripts, native modules, or deployment config. Contains build pipeline, signing, and environment setup. |
docs/USER_FLOWS.md |
Before modifying user-facing behavior. Contains step-by-step flows with edge cases — use as acceptance criteria. |
docs/MARKETER.md |
Before editing site/, adding media assets, or producing social/marketing content. Contains SEO rules, asset optimization standards, canonical URL rules, and the marketing content library. |
Read the relevant role doc(s) before starting work. Don't guess at conventions — they're documented.
Documentation Rules
MANDATORY: After any code change, you MUST update every affected doc before considering the task complete. This is not optional — stale docs break future sessions.
| What Changed | Docs to Update |
|---|---|
| CSS / colors / theme variables | docs/DESIGN.md color tables + docs/ARCHITECTURE.md if new variables added |
| User-facing behavior or UX | docs/USER_FLOWS.md flow steps + docs/PRODUCT.md if feature scope changed |
| New feature | docs/PRODUCT.md feature list + docs/USER_FLOWS.md new flow + docs/ARCHITECTURE.md if new files/IPC + README.md if major |
| Removed feature | Remove from docs/PRODUCT.md + docs/USER_FLOWS.md + README.md |
| Architecture / new files / IPC | docs/ARCHITECTURE.md directory tree + IPC table + data flow |
| Build / scripts / native modules | docs/DEVOPS.md scripts table + build pipeline |
| Code conventions changed | docs/ARCHITECTURE.md conventions section |
| New tool or annotation type | docs/PRODUCT.md tool table + docs/USER_FLOWS.md new tool flow + docs/ARCHITECTURE.md directory tree + README.md shortcut table |
| Theme system changes | docs/DESIGN.md + docs/ARCHITECTURE.md theme system section + docs/USER_FLOWS.md §8.4 |
| Marketing site / SEO / media assets | docs/MARKETER.md + update sitemap.xml lastmod + verify canonical URLs |
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 · 123 lines · 2,006 tokens per session scan A 2a95feb3fe09
snip CLAUDE.md is an instructions file published in the GitHub repository rixinhahaha/snip (323 stars, last pushed 4mo ago), licensed MIT. It adds 2,006 tokens to every session, about $0.0100 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.