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/panniantong/agent-reach/claude-mdgit clone --depth 1 https://github.com/Panniantong/Agent-ReachWhat 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.00604 | $0.00604 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
Agent-Reach 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agent-reach-mcp CLAUDE.md — 92% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project
Agent Reach — Python CLI + library that gives AI agents read/search access to 13 internet platforms. Positioning: installer + doctor + config tool. NOT a wrapper — after install, agents call upstream tools directly. Repo: github.com/Panniantong/Agent-Reach | License: MIT | Version: 1.5.0
Commands
pip install -e .— Dev installpytest tests/ -v— All testspytest tests/test_cli.py -v— CLI tests onlybash test.sh— Full integration test (creates venv, installs, runs doctor + channel tests)python -m agent_reach.cli doctor— Run diagnosticspython -m agent_reach.cli install --env=auto— Auto-configure
Structure
agent_reach/cli.py— CLI entry point (argparse)agent_reach/core.py— Core read/search routing logicagent_reach/config.py— Config management (YAML, env vars)agent_reach/doctor.py— Diagnostics engineagent_reach/channels/— One file per platform (twitter.py, reddit.py, youtube.py, etc.)agent_reach/channels/base.py— Base channel class (all channels inherit from this)agent_reach/integrations/mcp_server.py— MCP server integrationagent_reach/skill/— OpenClaw skill filesagent_reach/guides/— Usage guidestests/— pytest testsconfig/mcporter.json— MCP tool config
Conventions
- Python 3.10+ with type hints
- Each channel is a single file in
channels/, inherits fromBaseChannel - Channel contract: must implement
can_handle(url),read(url),search(query),check()methods - Use
logurufor logging,richfor CLI output - Commit format:
type(scope): message(one commit = one thing) - All upstream tool calls go through public API/CLI, never hack internals
Rules
- NEVER modify upstream open source projects' source code
- Agent Reach is a "glue layer" — only route and call, don't reimagine
- Version in THREE places must match:
pyproject.toml,__init__.py,tests/test_cli.py - Always new branch for changes, PR to main, never push to main directly
- Run
pytest tests/ -vbefore committing — all tests must pass - Cookie-based auth (Twitter, XHS): use Cookie-Editor export method only, no QR scan
- XHS login: Cookie-Editor browser export only (QR will hang)
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.
- yesterday First seen · 45 lines · 604 tokens per session scan A c4bafda1a66e
Agent-Reach CLAUDE.md is an instructions file published in the GitHub repository Panniantong/Agent-Reach (76,746 stars, last pushed 7d ago), licensed MIT. It adds 604 tokens to every session, about $0.0030 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
zero-api-key-web-search GEMINI.md
Gemini CLI instructions for wd041216-bit/zero-api-key-web-search, covering zero-api-key web search for gemini cli, install, minimum verification, when to trigger and what success looks like.
OpenBiliClaw CLAUDE.md
Instructions for whiteguo233/OpenBiliClaw, covering claude.md, project overview, build & development commands, python backend and browser extension (extension/).
bernstein copilot-instructions.md
Copilot instructions for sipyourdrink-ltd/bernstein, covering copilot instructions, architecture, key constraints, before committing and git rules.
lobu AGENTS.md
Instructions for lobu-ai/lobu, covering repo map, unrecoverable — never do these, facts you cannot derive, ship a change and how to work.
bili-music AGENTS.md
Instructions for Jmiao11/bili-music: 技术栈:Tauri(Rust 后端 + 网页前端);取音频以免登录游客直链为主、yt-dlp 兜底;目标打包成单个 exe.
jentic-one GEMINI.md
Instructions for jentic/jentic-one: Otherwise, read AGENTS.md — this repo's canonical agent guidance.