agentmods.dev

cold-outreach

cold-outreach is an agent for Claude Code from Elnora-AI/elnora-google-workspace. It costs 95 tokens per session (1,102 once invoked), scanned A, original, Apache-2.0.

An agent for running email outreach campaigns from a Google Sheets contact list. It can create or send outreach messages, look for replies, update the sheet, report campaign statistics, and enroll contacts from Apollo data.

In plain words
What is it for?
Use it to run outreach, review drafts before sending, scan for replies, check campaign status, or prepare contacts for a multi-step campaign.
Why use it?
It keeps contact lists, messages, replies, and campaign status connected, reducing manual email and spreadsheet work.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: model in frontmatter; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the google-workspace plugin — 13 skills, 4 commands, 1 agent shipped together

not rated 2repo yesterday A scan 95 tokens original Apache-2.0

Good fit Use it to run outreach, review drafts before sending, scan for replies, check campaign status, or prepare contacts for a multi-step campaign.

Compare 6 agents from other repositories ↓
View source ↗ Elnora-AI/elnora-google-workspace
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Elnora-AI/elnora-google-workspace
Claude Code
/plugin install google-workspace

Made for: Claude Code.

Or install google-workspace, the plugin that ships this one along with the rest of its 13 skills, 4 commands, 1 agent.

Wrote 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.

agentmods badge for cold-outreach

README.md
[![agentmods](https://agentmods.dev/badge/agents/elnora-ai/elnora-google-workspace/cold-outreach/github.svg)](https://agentmods.dev/agents/elnora-ai/elnora-google-workspace/cold-outreach)
Your own site
<a href="https://agentmods.dev/agents/elnora-ai/elnora-google-workspace/cold-outreach"><img src="https://agentmods.dev/badge/agents/elnora-ai/elnora-google-workspace/cold-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.

agentmods 80×15 button for cold-outreach

Your own site · 80×15
<a href="https://agentmods.dev/agents/elnora-ai/elnora-google-workspace/cold-outreach"><img src="https://agentmods.dev/badge/agents/elnora-ai/elnora-google-workspace/cold-outreach.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,102 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00095 $0.01102
Opus 5 $0.00048 $0.00551
Sonnet 5 $0.00019 $0.00220
Haiku 4.5 $0.00010 $0.00110

Measured 9d ago against content hash c1d2ad05d5b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

cold-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 9d 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.

agents/cold-outreach.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cold Outreach Agent

Send, scan, and track outreach email campaigns using a Google Sheets contact list.

CLI

CLI="python3 ${CLAUDE_PLUGIN_ROOT}/agents/cold_outreach_agent.py || python ${CLAUDE_PLUGIN_ROOT}/agents/cold_outreach_agent.py"

Commands

# Send outreach (creates drafts by default)
$CLI run --sheet SPREADSHEET_ID [--template cold-outreach-v1] [--account work] [--draft-first N] [--dry-run] [--compact]

# Scan inbox for replies and update sheet
$CLI scan --sheet SPREADSHEET_ID [--account work] [--since 2d] [--compact]

# Show campaign statistics
$CLI status --sheet SPREADSHEET_ID [--account work] [--compact]

# Enroll Apollo contacts into a campaign CSV for multi-step outreach
$CLI enroll --campaign CAMPAIGN_NAME --sequence SEQUENCE_NAME --input APOLLO_JSON_PATH [--dry-run] [--compact]

Safety Rules

  1. Always use --account work for outreach. Never send cold emails from main.
  2. Default is drafts. The run command creates drafts unless --draft-first N is set. With --draft-first N, the first N contacts are drafted for review and the rest are sent directly.
  3. Max 50 emails per batch. The agent hard-caps at 50 per invocation.
  4. Before first campaign: Do a --dry-run first, then create 3-5 drafts for the user to review.
  5. Ask the user before sending. Never auto-send without explicit approval.
  6. Respect do_not_email flags. Before building any campaign list, cross-reference against your suppression list (e.g. do-not-email.csv) and EXCLUDE any contact where do_not_email=true. These contacts explicitly opted out. This is non-negotiable.

Workflow

  1. Read the contact sheet: use the Google Workspace CLI to inspect the sheet first
  2. Do a dry run: $CLI run --sheet ID --account work --dry-run
  3. Create drafts: $CLI run --sheet ID --account work
  4. Ask the user to review drafts in Gmail
  5. After approval, send all: $CLI run --sheet ID --account work --draft-first 0
  6. Scan for replies: $CLI scan --sheet ID --account work --since 2d
  7. Check stats: $CLI status --sheet ID --account work

Read the full file on GitHub · 97 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. 9d ago First seen · 97 lines · 95 tokens per session scan A c1d2ad05d5b9

Subscribe to this mod's changes

cold-outreach is an agent published in the GitHub repository Elnora-AI/elnora-google-workspace (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 95 tokens to every session and 1,102 once invoked, about $0.0005 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.

Claude CodeMarketing and SEOclaude-code-plugincligmailgoogle-calendargoogle-drive
Related

Other agents, from other repositories

architect

System design expert for architecture reviews, pattern analysis, SOLID principles evaluation, and coupling/abstraction assessments. Use when reviewing structural changes, evaluating design decisions, or analyzing system architecture.

restarter/lets-workflow · 39 tokens

backend

Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.

restarter/lets-workflow · 39 tokens

resy-agent

Resy-specific booking agent. Handles venue search, availability, book, snipe, list, and cancel via the restaurant CLI with --provider resy.

omarshahine/restaurant-cli · 39 tokens

database

Database expert for schema design review, migration analysis, query optimization, index assessment, and transaction safety. Use when reviewing database schemas, migrations, ORM code, or raw queries.

restarter/lets-workflow · 37 tokens

frontend

Frontend development expert for UI component review, state management analysis, accessibility assessment, and bundle optimization. Use when reviewing React, Vue, TypeScript, CSS, or any client-side code.

restarter/lets-workflow · 39 tokens

linear-issue-creator

Create Linear issues from user descriptions. NOT for URLs — use linear-url-to-issues for that. Use when: "create issue", "new ticket", "log bug", "add task", "file issue", "report bug", "make ticket", "make issue", "add to linear", "create task", "new issue", "make new issue", "make new ticket", "make new linear…

Elnora-AI/elnora-linear · 175 tokens