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/agricidaniel/dataforseo-brain/claude-mdgit clone --depth 1 https://github.com/AgriciDaniel/dataforseo-brainWrote 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/agricidaniel/dataforseo-brain/claude-md)<a href="https://agentmods.dev/instructions/agricidaniel/dataforseo-brain/claude-md"><img src="https://agentmods.dev/badge/instructions/agricidaniel/dataforseo-brain/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 | $0.00051 | $0.00051 |
| Opus 5 | $0.00026 | $0.00026 |
| Sonnet 5 | $0.00010 | $0.00010 |
| Haiku 4.5 | $0.00005 | $0.00005 |
Grade A, and why
dataforseo-brain 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 5d 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.
This is a copy
95% identical to youtuber CLAUDE.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
DataForSEO Brain Claude Instructions
@AGENTS.md
Claude-specific note: this file is persistent project context, not an
enforcement layer. Release readiness is enforced by scripts/audit_brain.py
and scripts/package_release.py.
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.
- 5d ago First seen · 8 lines · 51 tokens per session scan A 923f33fed644
dataforseo-brain CLAUDE.md is an instructions file published in the GitHub repository AgriciDaniel/dataforseo-brain (48 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to youtuber CLAUDE.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
llm-wiki-agent GEMINI.md
Gemini CLI instructions for SamurAIGPT/llm-wiki-agent, covering llm wiki agent — schema & workflow instructions, how to use, directory layout, page format and ingest workflow.
obsidian-wiki AGENTS.md
AGENTS.md instructions for Ar9av/obsidian-wiki, covering obsidian wiki — agent context, readme translation parity, configuration, targeting a specific vault and vault structure.
llm-wiki-compiler AGENTS.md
AGENTS.md instructions for atomicstrata/llm-wiki-compiler, covering llmwiki, development guidelines, code style & standards, clean code rules and comments and documentation.
BITE AGENTS.md
Instructions for RipeMangoBox/BITE, covering agent guide, working surface, local pipeline, branch sync policy and rules.
hippocampus AGENTS.md
Instructions for sturlese/hippocampus: Read and follow CLAUDE.md in the repository root completely before doing any work. It is the canonical project contract, written for Claude Code as the native host; its vault rules and workflows apply unchanged to Codex.
llm-knowledge-bases CLAUDE.md
Instructions for rvk7895/llm-knowledge-bases, covering claude.md -- project instructions, project identity, configuration, skills and formatting rules (obsidian-compatible).