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/topheman/effect-viz/agents-mdgit clone --depth 1 https://github.com/topheman/effect-vizWhat 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.01240 | $0.01240 |
| Opus 5 | $0.00620 | $0.00620 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
effect-viz AGENTS.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 3d 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.
- 3d ago First seen · 129 lines · 1,240 tokens per session scan A 7493eae38c21
effect-viz AGENTS.md is an instructions file published in the GitHub repository topheman/effect-viz (46 stars, last pushed 6d ago), with no licence file. It adds 1,240 tokens to every session, about $0.0062 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
pygwalker AGENTS.md
Instructions for Kanaries/pygwalker, covering agents.md — pygwalker contributor & agent guide, 1. what pygwalker is (30-second model), 2. repo map, 3. how the two halves fit together (build & load model) and 4. first-time setup.
pygwalker CLAUDE.md
Instructions for Kanaries/pygwalker, covering claude.md and tl;dr for a coding agent.
neko-master AGENTS.md
Instructions for foru17/neko-master, covering agents.md, scope and priorities, skills (task-specific workflow guides), repository overview and project map (key files).
semiotic CLAUDE.md
Claude Code instructions for nteract/semiotic, covering semiotic claude code instructions and claude code notes.
IoTSharp AGENTS.md
Instructions for IoTSharp/IoTSharp, covering agents.md, current mission, current priority order, current concept realignment and ai workbench direction.
neko-master CLAUDE.md
Instructions for foru17/neko-master: All repo guidance lives in AGENTS.md — commands, conventions, key contracts, and the project map. Read it first.