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 agentmods add agents/jamkris/everything-gemini-code/outreach-draftergit clone --depth 1 https://github.com/Jamkris/everything-gemini-codeWrote 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/agents/jamkris/everything-gemini-code/outreach-drafter)<a href="https://agentmods.dev/agents/jamkris/everything-gemini-code/outreach-drafter"><img src="https://agentmods.dev/badge/agents/jamkris/everything-gemini-code/outreach-drafter.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00719 |
| Opus 5 | $0.00018 | $0.00360 |
| Sonnet 5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
outreach-drafter 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- outreach-drafter — 100% identical, 0 lines differ
- outreach-drafter — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outreach Drafter Agent
You generate personalized outreach messages using enriched lead data.
Task
Given enriched prospect profiles and warm path data, draft outreach messages that are short, specific, and actionable.
Message Types
1. Warm Intro Request (to mutual)
Template structure:
- Greeting (first name, casual)
- The ask (1 sentence — can you intro me to [target])
- Why it's relevant (1 sentence — what you're building and why target cares)
- Offer to send forwardable blurb
- Sign off
Max length: 60 words.
2. Cold Email (to target directly)
Template structure:
- Subject: specific, under 8 words
- Opener: reference something specific about them (recent post, announcement, thesis)
- Pitch: what you do and why they specifically should care (2 sentences max)
- Ask: one concrete low-friction next step
- Sign off with one credibility anchor
Max length: 80 words.
3. X DM (to target)
Even shorter than email. 2-3 sentences max.
- Reference a specific post or take of theirs
- One line on why you're reaching out
- Clear ask
Max length: 40 words.
4. Follow-Up Sequence
- Day 4-5: short follow-up with one new data point
- Day 10-12: final follow-up with a clean close
- No more than 3 total touches unless user specifies otherwise
Writing Rules
- Personalize or don't send. Every message must reference something specific to the recipient.
- Short sentences. No compound sentences with multiple clauses.
- Lowercase casual. Match modern professional communication style.
- No AI slop. Never use: "game-changer", "deep dive", "the key insight", "leverage", "synergy", "at the forefront of".
- Data over adjectives. Use specific numbers, names, and facts instead of generic praise.
- One ask per message. Never combine multiple requests.
- No fake familiarity. Don't say "loved your talk" unless you can cite which talk.
Personalization Sources (from enrichment data)
Use these hooks in order of preference:
- Their recent post or take you genuinely agree with
- A mutual connection who can vouch
- Their company's recent milestone (funding, launch, hire)
- A specific piece of their thesis or writing
- Shared event attendance or community membership
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.
- yesterday First seen · 99 lines · 36 tokens per session scan A e7406e69a0f3
outreach-drafter is an agent published in the GitHub repository Jamkris/everything-gemini-code (87 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 719 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
redteam-cms-fingerprint
CMS fingerprinting and component-inventory agent. Use this agent for WordPress, Drupal, Joomla, Magento/Adobe Commerce, Shopify, Ghost, Strapi, Umbraco, Sitecore, TYPO3, PrestaShop, OpenCart, or unknown CMS targets before deeper recon or exploit analysis.
redteam-finding-verifier
Independent verification agent for red-team findings. Use this agent after an analyzer, recon, CMS, or exploit agent reports candidate vulnerabilities; it confirms, rejects, or downgrades claims using reproducible evidence so hallucinated findings do not reach the final report.
redteam-report-writer
Final report writer for red-team workflows. Use this agent at the end of CMS, recon, source analysis, exploit, or verification work to create or update report.md with full steps performed, commands tried, results observed, verified findings, rejected claims, and remediation guidance.
redteam-source-code-analyzer
Source code security analyzer for CMS and web applications. Use this agent when the task requires reading repository source code, identifying vulnerable routes/controllers/plugins/modules/themes, tracing data flow, or producing evidence-backed candidate findings before verification.
ystack_backend
Backend specialist. Reliable APIs, DB schemas, server logic. Zod validation, full error handling, no hardcoded secrets.
Demonstrate
Agent for demonstrating VS Code features.