Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/vmafx/vmafx/claude-mdgit clone --depth 1 https://github.com/VMAFx/vmafxWhat 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 | $0.05854 | $0.05854 |
| Opus 5 | $0.02927 | $0.02927 |
| Sonnet 5 | $0.01171 | $0.01171 |
| Haiku 4.5 | $0.00585 | $0.00585 |
Grade A, and why
vmafx 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 402 lines · 5,854 tokens per session scan A 60bb6a994503
vmafx CLAUDE.md is an instructions file published in the GitHub repository VMAFx/vmafx (5 stars, last pushed 2d ago), with no licence file. It adds 5,854 tokens to every session, about $0.0293 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
rustfs CLAUDE.md
Instructions for rustfs/rustfs, covering rustfs — claude.md, commands, where to look (do not duplicate here) and domain conventions worth knowing up front.
openscreen AGENTS.md
Instructions for getopenscreen/openscreen, covering agents.md, setup commands, development principles, project layout and code style.
Grace AGENTS.md
Instructions for ScottArbeit/Grace, covering agent instructions, agent quickstart (local), issue tracking, development process and markdown guidelines.
erm AGENTS.md
Instructions for dougcalobrisi/erm, covering agents.md — erm, install, fallback (no uv on path), use — the iterate loop and tune — five knob clusters.
vibeframe AGENTS.md
Instructions for vericontext/vibeframe, covering agents.md, repository shape, commands, cli shape and agent workflow rules.
movi-player AGENTS.md
Instructions for MrUjjwalG/movi-player, covering agents.md — movi-player for ai coding assistants, 1. what this is, 2. package entry points, 3. architecture map and 4. the web component .