Borrowing it
Nothing to install: this file belongs to arnaudgelas/K-Ops. 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/arnaudgelas/K-Ops/main/CLAUDE.mdgit clone --depth 1 https://github.com/arnaudgelas/K-OpsWrote 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/arnaudgelas/k-ops/claude-md)<a href="https://agentmods.dev/instructions/arnaudgelas/k-ops/claude-md"><img src="https://agentmods.dev/badge/instructions/arnaudgelas/k-ops/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.00642 | $0.00642 |
| Opus 5 | $0.00321 | $0.00321 |
| Sonnet 5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
K-Ops 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This repository is an Obsidian-aligned living research vault. The same operating contract should work whether the active CLI is Claude Code, Codex CLI, or Gemini CLI.
Canonical rules: see OPERATING_RULES.md.
Mission
Turn raw sources into a durable Markdown knowledge base. Every answer should either:
- reference existing vault notes, or
- improve the vault if durable new knowledge was produced.
Operating rules
- Treat
data/raw/as immutable source evidence. - Treat
notes/as the curated Obsidian vault. - Treat
research/as the active run workspace for resumable research jobs, not as a substitute for the curated vault. - Prefer updating existing concept pages instead of creating duplicates.
- Keep always-on instructions short; move command detail into runbooks, skills, or templates.
- Every concept page should link to related pages and relevant source summaries.
- Record contradictions, uncertainties, and missing evidence explicitly.
- Do not silently invent citations.
- Treat imported model-generated reports as leads that must be verified against primary sources before they can shape concept pages.
- If a question cannot be answered from the vault, say so and propose the minimum fetch needed.
Default workflow
- Read relevant source summaries in
notes/Sources/. - Read the linked concept pages in
notes/Concepts/. - Use
notes/Runbooks/Agent_Workflow_Quick_Reference.mdwhen you need command syntax or command order. - Answer from the vault.
- If the answer yields durable knowledge, file it back into the vault.
- Run
lintafter structural edits. - Update
notes/Home.mdandnotes/TODO.mdwhen the vault's structure or gaps change.
Research runs
When a topic needs a full research run, use the resumable workflow in research/:
- create a brief, status checkpoint, and progress log
- record the
quality_tierasfast,standard, ordeep - collect sources into
notes/Sources/ - write findings, run a contrarian review, then draft the final report
- archive completed runs with a manifest that lists every moved artifact
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 · 68 lines · 642 tokens per session scan A 185698f4b2c5
K-Ops CLAUDE.md is an instructions file published in the GitHub repository arnaudgelas/K-Ops (1 stars, last pushed 17d ago), licensed MIT. It adds 642 tokens to every session, about $0.0032 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.