Agent-Reach CLAUDE.md

A project instruction file for Agent-Reach, a Python command-line tool and library that lets AI agents read and search information from internet platforms. It documents the project’s commands, structure, conventions, and tests.

In plain words
What is it for?
Use it when developing Agent-Reach, running its tests or diagnostics, configuring installations, or working on its platform integrations.
Why use it?
It gives Claude Code the project context needed to make changes that fit the existing codebase and to run the right checks.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/panniantong/agent-reach/claude-md
Clone the repo
git clone --depth 1 https://github.com/Panniantong/Agent-Reach
Per session 604 This file is loaded in full into every session.
When invoked 604 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash c4bafda1a66e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

CLAUDE.md · 45 lines

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 install
  • pytest tests/ -v — All tests
  • pytest tests/test_cli.py -v — CLI tests only
  • bash test.sh — Full integration test (creates venv, installs, runs doctor + channel tests)
  • python -m agent_reach.cli doctor — Run diagnostics
  • python -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 logic
  • agent_reach/config.py — Config management (YAML, env vars)
  • agent_reach/doctor.py — Diagnostics engine
  • agent_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 integration
  • agent_reach/skill/ — OpenClaw skill files
  • agent_reach/guides/ — Usage guides
  • tests/ — pytest tests
  • config/mcporter.json — MCP tool config

Conventions

  • Python 3.10+ with type hints
  • Each channel is a single file in channels/, inherits from BaseChannel
  • Channel contract: must implement can_handle(url), read(url), search(query), check() methods
  • Use loguru for logging, rich for 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/ -v before 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)

Read the full file on GitHub · 45 lines

Changes

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.

  1. yesterday First seen · 45 lines · 604 tokens per session scan A c4bafda1a66e

Subscribe to this mod's changes

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.