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 AlexisMarasigan/coldoutboundskills --skill cold-email-kickoffgit clone --depth 1 https://github.com/AlexisMarasigan/coldoutboundskillsWrote 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/alexismarasigan/coldoutboundskills/cold-email-kickoff)<a href="https://agentmods.dev/skills/alexismarasigan/coldoutboundskills/cold-email-kickoff"><img src="https://agentmods.dev/badge/skills/alexismarasigan/coldoutboundskills/cold-email-kickoff/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/alexismarasigan/coldoutboundskills/cold-email-kickoff"><img src="https://agentmods.dev/badge/skills/alexismarasigan/coldoutboundskills/cold-email-kickoff.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.00097 | $0.01950 |
| Opus 5 | $0.00048 | $0.00975 |
| Sonnet 5 | $0.00019 | $0.00390 |
| Haiku 4.5 | $0.00010 | $0.00195 |
Grade A, and why
cold-email-kickoff 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.
This is a copy
100% identical to cold-email-kickoff — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Email Kickoff
The single entry point for a fresh user. Replaces "stare at 29 skills and guess which to run first."
When to use
- First-time cold email operator on this repo
- New client/business being onboarded (fresh
profiles/<slug>/directory) - Experienced operator starting a new campaign for a new business
- Anyone who asks "where do I start?"
What this skill produces
- A populated
profiles/<business-slug>/client-profile.yaml(from/icp-onboarding) - A
profiles/<business-slug>/lead-magnets.mdwith the chosen free offer - A
profiles/<business-slug>/campaign-strategy.mdwith 15-25 campaign ideas - A consolidated
profiles/<business-slug>/campaign-plan.md— a single-page summary you can show stakeholders - An interactive menu pointing at the right next skill based on your infrastructure status
Flow
Step 1 (asked FIRST): Infrastructure status
Before touching any business context, ask:
- "Do you already have sending domains + inboxes set up on Smartlead?" (yes / no / not sure)
- "At least 20 inboxes that have been warming for 2+ weeks?" (yes / no)
- "Do you have API keys for Smartlead + Prospeo + MillionVerifier in your
.env?" (yes / partial / no)
These answers determine the next-step menu at Step 6. Save them as infrastructure_status in the profile.
Step 2: Load or create the business profile
Check for profiles/<business-slug>/client-profile.yaml:
- Exists → load it. Ask: "Use this existing profile (answer:
use) or start fresh (answer:new)?" - Doesn't exist → invoke
/icp-onboarding. This scrapes the user's website first, then interviews them. Produces the profile.
Step 3: Ensure lead magnet is chosen
Check the loaded/created profile for a lead_magnet field:
- Empty → invoke
/lead-magnet-brainstorm. It asks 4 intake questions, scores 10 magnet archetypes, picks a top 2-3, updates the profile. - Already set → confirm with the user: "Using
<chosen magnet>as your free offer. OK?" — if they want to change it, re-invoke/lead-magnet-brainstorm.
What ships with it
3 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 · 174 lines · 97 tokens per session scan A ff97d030fa3f
cold-email-kickoff is a skill published in the GitHub repository AlexisMarasigan/coldoutboundskills (4 stars, last pushed 4mo ago), licensed MIT. It adds 97 tokens to every session and 1,950 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cold-email-kickoff, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…