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 skills add anthroos/heyreach-claude-skill --skill heyreach-claude-skillgit clone --depth 1 https://github.com/anthroos/heyreach-claude-skillWrote 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/skills/anthroos/heyreach-claude-skill/heyreach-claude-skill)<a href="https://agentmods.dev/skills/anthroos/heyreach-claude-skill/heyreach-claude-skill"><img src="https://agentmods.dev/badge/skills/anthroos/heyreach-claude-skill/heyreach-claude-skill/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/anthroos/heyreach-claude-skill/heyreach-claude-skill"><img src="https://agentmods.dev/badge/skills/anthroos/heyreach-claude-skill/heyreach-claude-skill.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00063 | $0.02569 |
| Opus 5 | $0.00032 | $0.01285 |
| Sonnet 5 | $0.00013 | $0.00514 |
| Haiku 4.5 | $0.00006 | $0.00257 |
Grade A, and why
heyreach scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> connected, ALWAYS call the `heyreach.*` MCP tools. Do **not** curl the REST API. Reach for REST only How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HeyReach LinkedIn Automation (Claude skill)
Drive HeyReach entirely from Claude. HeyReach is API-first, so you never babysit browser automation or VM queues — campaigns run in HeyReach's cloud with built-in warmup.
Setup
- HeyReach account: https://heyreach.io/?via=ivanrx
- Pick ONE transport. MCP and REST use different credentials from different sub-sections of
Settings → Integrations — do not mix them up:
- MCP (recommended): Settings → Integrations → MCP Server → Get MCP key → copy the
MCP Connection URL (the key is already baked into the URL). Then:
claude mcp add --scope user --transport http heyreach '<MCP Connection URL>'Restart Claude so theheyreach.*tools load. Verify:claude mcp list→heyreach … connected. - REST (fallback): Settings → Integrations → API → copy the API key (a SEPARATE key from the
MCP key). Base
https://api.heyreach.io/api/public/, headerX-API-KEY: <key>.
- MCP (recommended): Settings → Integrations → MCP Server → Get MCP key → copy the
MCP Connection URL (the key is already baked into the URL). Then:
Transport decision — check this first, every session. If
claude mcp listshowsheyreachconnected, ALWAYS call theheyreach.*MCP tools. Do not curl the REST API. Reach for REST only when no MCP server is connected and you actually have anX-API-KEY. Hitting REST without a key returns401 Unauthorized— that means "wrong transport / missing key", not "service is down".
Core model
The API drives CAMPAIGNS (sequences), not individual clicks. You don't "send a connect to X" ad-hoc. You create a campaign with a sequence (connection request → wait → message → follow-up) and push leads into it; HeyReach executes from the cloud with warmup and rate limits.
Sourcing leads — the API does NOT search LinkedIn
There is no "find people" tool. HeyReach ingests leads you already have (add_leads_to_list /
add_leads_to_campaign take profileUrl / navigatorProfileId); it does not run a LinkedIn people-search
for you. So "find 10 X" is a research step you do first, then push the results in.
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.
- 12d ago First seen · 147 lines · 63 tokens per session scan A 001ab75888d9
heyreach is a skill published in the GitHub repository anthroos/heyreach-claude-skill (5 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 2,569 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…