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 realjaymes/marketingagentskills --skill outbound-enginegit clone --depth 1 https://github.com/realjaymes/marketingagentskillsWrote 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/realjaymes/marketingagentskills/outbound-engine)<a href="https://agentmods.dev/skills/realjaymes/marketingagentskills/outbound-engine"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/outbound-engine/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/realjaymes/marketingagentskills/outbound-engine"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/outbound-engine.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.00164 | $0.04075 |
| Opus 5.5 | $0.00066 | $0.01630 |
| Sonnet 5.5 | $0.00033 | $0.00815 |
| Haiku 4.5 | $0.00016 | $0.00407 |
Grade A, and why
outbound-engine 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 2d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outbound Engine
The campaign half of cold outbound. It takes the enriched, scored prospect list from prospect-scraper and runs it to booked calls: personalize → assemble the sequence → QA in the preview tool → warm the sending infrastructure → send through Smartlead → measure → file every reply and handle real prospects through to close.
prospect-scraper owns FIND, ENRICH, VERIFY, SCORE and signal detection. This skill owns PERSONALIZE, QA, WARMUP, SEND, MEASURE and reply filing. They meet at the common record schema.
When to use
- Build or personalize a cold-email sequence (
{{gap}}, signals, spintax, Liquid). - Build or regenerate the HTML preview and QA tool, the review surface.
- Prepare a Smartlead-ready list and run or scale a campaign.
- Check a live or completed campaign's replies, file them, or handle a prospect who replied.
Use a different skill for finding and enriching leads (prospect-scraper), standalone copy, or Clay-specific work.
Where things live
- Runnable code (generators, the preview builder, verifiers) lives in a version-controlled repo.
- Lead lists and the preview tool live in one local folder per campaign. The master
*-leads.csvis Smartlead-ready, and the* Email Preview.htmlfile is the review surface. - Your notes system (Obsidian, Notion, a docs folder) holds the logic: the offer, the
{{gap}}logic, and the sequence templates with{{}}and spintax. It never holds individually filled emails. Once a campaign is live, it also holds the campaign'sRepliesfile and each real prospect's own file (see Reply filing below), because those track decisions. - The preview tool shows the final rendered emails. You review there, not in the notes.
- Flow: enriched list →
{{gap}}and variant → master CSV → preview tool (QA) → export cleaned → Smartlead → run → file replies and handle prospects. Push to Smartlead when the batch reaches the campaign's target size.
Keep every note current. When a fact changes, rewrite the affected section in place instead of appending dated updates. A sequence template doc always shows only the current copy. The Replies file is the one designated log, with one row per reply.
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.
- 2d ago First seen · 107 lines · 164 tokens per session scan A 3e281dedb954
outbound-engine is a skill published in the GitHub repository realjaymes/marketingagentskills (68 stars, last pushed 2d ago), licensed MIT. It adds 164 tokens to every session and 4,075 once invoked, about $0.0007 per session on Opus 5.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-10-24.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…