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.
git clone --depth 1 https://github.com/TheophilusChinomona/claude-openclaw-pluginWrote 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/commands/theophiluschinomona/claude-openclaw-plugin/oc-outreach)<a href="https://agentmods.dev/commands/theophiluschinomona/claude-openclaw-plugin/oc-outreach"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-outreach/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/commands/theophiluschinomona/claude-openclaw-plugin/oc-outreach"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-outreach.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.00010 | $0.01299 |
| Opus 5 | $0.00005 | $0.00649 |
| Sonnet 5 | $0.00002 | $0.00260 |
| Haiku 4.5 | $0.00001 | $0.00130 |
Grade A, and why
oc-outreach 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/oc-outreach Command
Scaffold and manage a research-first outreach agent with cold email pipeline, human voice standard, and prompt injection protection.
Subcommands
setup — Interactive Scaffolding
Scaffold a complete outreach agent workspace under team/outreach/.
Steps
-
Detect workspace root. Look for
.openclaw/workspace-state.jsonorCLAUDE.mdin the current directory and parent directories. If not found, ask the user for the workspace path. -
Check prerequisites:
team/directory exists (create if missing after confirming)skills/imap-smtp-email/exists in workspace (warn if missing — outreach will work for everything except actual email sending)
-
Collect configuration values interactively. Ask the user for each value, showing the default in parentheses:
BUSINESS_NAME— Business domain/name for sign-offs (e.g. "theochinomona.tech")BD_PERSON_NAME— Name the outreach agent signs emails as (e.g. "Zach")BD_TITLE— Title in email sign-off (default: "Business Development")OWNER_NAME— Workspace owner's first name (e.g. "Theo")OWNER_TIMEZONE— Owner's timezone (e.g. "SAST (UTC+2)")SENDER_EMAIL— Email address to send from (e.g. "[email protected]")DISPLAY_NAME— Display name on sent emails (e.g. "John Smith")EMAIL_SKILL_PATH— Auto-detect from workspace, confirm with user
-
Read all templates from
skills/openclaw-outreach-setup/references/file-templates.mdin the plugin directory. -
Create the full directory structure:
team/outreach/ team/outreach/memory/ team/outreach/pipeline/ team/outreach/pipeline/templates/ team/outreach/pipeline/prospects/ team/outreach/skills/cold-outreach/ team/outreach/skills/client-discovery/ team/outreach/skills/proposal-writing/ -
Generate each file from templates with all
{{PLACEHOLDER}}values replaced with the collected config values. Also replace{{WORKSPACE_ROOT}}with the detected workspace root path and{{EMAIL_SKILL_PATH}}with the email skill path.
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 · 127 lines · 10 tokens per session scan A 28ede22814f2
oc-outreach is a command published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 1,299 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.