Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TheophilusChinomona/claude-openclaw-pluginnpx agentmods add skills/theophiluschinomona/claude-openclaw-plugin/openclaw-outreach-setupWrote 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/theophiluschinomona/claude-openclaw-plugin/openclaw-outreach-setup)<a href="https://agentmods.dev/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-outreach-setup"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-outreach-setup/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/theophiluschinomona/claude-openclaw-plugin/openclaw-outreach-setup"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-outreach-setup.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.00064 | $0.01835 |
| Opus 5 | $0.00032 | $0.00918 |
| Sonnet 5 | $0.00013 | $0.00367 |
| Haiku 4.5 | $0.00006 | $0.00184 |
Grade A, and why
openclaw-outreach-setup 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outreach Agent Setup
End-to-end guide for scaffolding a research-first outreach agent in an OpenClaw workspace. Based on a production outreach agent that handles B2B prospecting, personalized cold email, pipeline tracking, and autonomous response handling.
Overview
The outreach agent (default name: Reef) is a specialist agent that:
- Discovers prospects matching configured target verticals
- Researches each prospect deeply before any outreach
- Drafts personalized cold emails using proven copy frameworks
- Tracks a full pipeline from identification through conversion
- Handles routine responses autonomously with prompt injection protection
- Escalates pricing, proposals, and commitments to the owner
Architecture
team/outreach/
CLAUDE.md # Full agent instructions (workflow, pipeline, voice, safety)
AGENTS.md # Agent role, handoff protocol, boundaries
SOUL.md # Core identity and principles
IDENTITY.md # Name, role, vibe
USER.md # Owner preferences
TOOLS.md # Tool configuration with paths
HEARTBEAT.md # Empty specialist stub
MEMORY.md # Curated long-term memory (empty at setup)
pipeline/
verticals.md # Target categories (owner configures)
tracker.json # Pipeline state — all prospects
templates/
prospect-brief.md # Research brief template
email-sequence.md # Email sequence template with voice checklist
prospects/ # Per-prospect directories (created during operation)
skills/
cold-outreach/
SKILL.md # Copy frameworks (PAS, BAB, AIDA, one-liner)
human-voice.md # Human voice standard and pre-send checklist
client-discovery/
SKILL.md # 5-phase qualification framework
proposal-writing/
SKILL.md # SCR proposal framework
Configuration Parameters
The setup command collects these values to personalize the agent:
| Parameter | Description | Example |
|---|---|---|
BUSINESS_NAME |
Business domain/name used in sign-offs | theochinomona.tech |
BD_PERSON_NAME |
Name the outreach agent signs emails as | Zach |
BD_TITLE |
Title in email sign-off | Business Development |
OWNER_NAME |
Workspace owner's first name | Theo |
OWNER_TIMEZONE |
Owner's timezone for scheduling | SAST (UTC+2) |
SENDER_EMAIL |
Email address to send from | [email protected] |
DISPLAY_NAME |
Display name on sent emails | Theo Chinomona |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 202 lines · 64 tokens per session scan A c463a1a2bf58
openclaw-outreach-setup is a skill published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 1,835 once invoked, about $0.0003 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.