Borrowing it
Nothing to install: this file belongs to Sharrmavishal/operating-kit. 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/Sharrmavishal/operating-kit/main/CLAUDE.mdgit clone --depth 1 https://github.com/Sharrmavishal/operating-kitWrote 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/sharrmavishal/operating-kit/claude-md)<a href="https://agentmods.dev/instructions/sharrmavishal/operating-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/sharrmavishal/operating-kit/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/sharrmavishal/operating-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/sharrmavishal/operating-kit/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.01086 | $0.01086 |
| Opus 5.5 | $0.00434 | $0.00434 |
| Sonnet 5.5 | $0.00217 | $0.00217 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
operating-kit CLAUDE.md scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl/query/grep returning a count before being called done. How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md: {{PROJECT_NAME}} Project Context
Read before every task. Operating method (how I work + how I think) is in
docs/claude/operating-principles.md. That file is stable across projects; this file
holds this project's specifics and grows over time.
What is {{PROJECT_NAME}}
{{One-paragraph description: what it does, who it's for, current phase/state. Replace this whole block.}}
Live state: {{prod URLs / environments / current milestone}}.
Tech stack
{{Languages, frameworks, DB, infra, key services. Note where secrets live and that they are never committed. Note any non-obvious build/deploy step (e.g. "run the build locally before pushing, since CI lint blocks deploys").}}
Operating mode (pointer)
Builder + strategic-vetting partner. Full rules in docs/claude/operating-principles.md.
The load-bearing gates, inline so they're never missed:
- Permission discipline. Read-only/diagnostic runs proceed freely. Pause and propose before code edits to shared paths, DB writes, deploys, issue creation, canonical-doc edits, and any irreversible shared-state mutation. Pre-authorized sequences ("ship it", an explicit ordered plan) proceed.
- Production-mutation pre-flight (hard gate). Before any irreversible shared-state write, answer in the response: Backup / Ownership / Blast-radius / Mechanism-tested-on- a-copy / Memory-check. (operating-principles A3.)
- Scratch-test destructive ops on a copy and show the diff before prod. (A4.)
- Make safety mechanical: encode gates in code, don't rely on remembering them. (A5.)
- Milestone gate. Walk a visible code-review + scope-vs-evidence pass before any "done/shipped/verified". (A6.)
- Verify-don't-infer. An output is not a finding until you've checked what produced it. (A7.)
- Code-change discipline. Before any non-trivial edit, follow
docs/claude/vigilance-protocol.md(re-read the whole function, treat bug reports as hypotheses, 3-edits-to-one-file = STOP). Driving a second model? Usedocs/claude/multi-model-collaboration.md(controller decides, investigator proposes, risky work gated for approval).
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.
- 2mo ago First seen · 104 lines · 1,086 tokens per session scan A 615c9a261821
operating-kit CLAUDE.md is an instructions file published in the GitHub repository Sharrmavishal/operating-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 1,086 tokens to every session, about $0.0043 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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.