Borrowing it
Nothing to install: this file belongs to romovpa/claudini. 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/romovpa/claudini/main/CLAUDE.mdgit clone --depth 1 https://github.com/romovpa/claudiniWrote 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/romovpa/claudini/claude-md)<a href="https://agentmods.dev/instructions/romovpa/claudini/claude-md"><img src="https://agentmods.dev/badge/instructions/romovpa/claudini/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.01257 | $0.01257 |
| Opus 5 | $0.00629 | $0.00629 |
| Sonnet 5 | $0.00251 | $0.00251 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
claudini 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 7d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claudini — Developer Guide
Package manager
Use uv for everything. uv run -m ... to execute, uv add to install dependencies. Never use pip install.
Running benchmarks
# Run a preset (all methods, all samples)
uv run -m claudini.run_bench random_valid
# Override method, sample, seed, budget from CLI
uv run -m claudini.run_bench random_valid --method gcg,acg --sample 0 --seed 0
uv run -m claudini.run_bench safeguard_valid --method gcg --max-flops 1e15
# Smoke test (use /tmp to avoid polluting results/)
uv run -m claudini.run_bench random_train --method gcg --sample 0 --max-flops 1e12 --results-dir /tmp/smoke
Results save to results/<method>/<preset_name>/<model>/sample_<S>_seed_<N>.json. Existing results are auto-skipped.
Config files
Preset YAML files in configs/ define the full experiment specification:
model: Qwen/Qwen2.5-7B-Instruct
optim_length: 15
max_flops: 1.0e+17
dtype: bfloat16
samples: [0, 1, 2, 3, 4]
seeds: [0]
input_spec:
source: { type: random, query_len: 0, target_len: 10 }
layout: { type: suffix }
init: { type: random }
method_kwargs: # optional per-method hyperparameter overrides
acg: { num_coords: 3 }
CLI flags override any preset value.
Adding a new method
- Create a directory under
claudini/methods/(e.g.claudini/methods/claude/v125/) - Add
optimizer.pyand__init__.py - Subclass
TokenOptimizer(fromclaudini.base), setmethod_nameas a class variable:
from claudini.methods.original.gcg import GCGOptimizer
class MyOptimizer(GCGOptimizer):
method_name = "claude_v125"
def setup(self, prompt, target):
super().setup(prompt, target)
# custom setup
def step(self, step_num):
# must call self.flop_counter for every model pass
self.flop_counter.count_forward(n_tokens)
# ...
return (discrete_loss, soft_loss_or_None, suffix_string)
- In
__init__.py:from .optimizer import MyOptimizer - Run:
uv run -m claudini.run_bench random_train --method claude_v125
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.
- 7d ago First seen · 134 lines · 1,257 tokens per session scan A 6a1b69bfee8d
claudini CLAUDE.md is an instructions file published in the GitHub repository romovpa/claudini (241 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 1,257 tokens to every session, about $0.0063 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.