build-sequences

build-sequences is a skill for Claude Code from hunter-io/claude-plugin. It costs 72 tokens per session (2,207 once invoked), scanned A, original, MIT.

A workflow for creating and running Hunter email sequences, which send planned follow-up messages to selected contacts over time.

In plain words
What is it for?
It is for creating outreach sequences, adding follow-up messages and leads, starting or pausing campaigns, resuming them, and checking sequence statistics.
Why use it?
It removes the need to configure sequences, recipients, launches, pauses, and performance checks manually across separate steps. The first email still has to be written in Hunter’s dashboard because its API is unavailable.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the hunter plugin — 13 skills, 1 MCP server shipped together

Good fit It is for creating outreach sequences, adding follow-up messages and leads, starting or pausing campaigns, resuming them, and checking sequence statistics.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hunter-io/claude-plugin/build-sequences
Install

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.

Any agent
npx skills add hunter-io/claude-plugin --skill build-sequences
Clone the repo
git clone --depth 1 https://github.com/hunter-io/claude-plugin

Made for: Claude Code.

Or install hunter, the plugin that ships this one along with the rest of its 13 skills, 1 MCP server.

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 build-sequences

README.md
[![agentmods](https://agentmods.dev/badge/skills/hunter-io/claude-plugin/build-sequences/github.svg)](https://agentmods.dev/skills/hunter-io/claude-plugin/build-sequences)
Your own site
<a href="https://agentmods.dev/skills/hunter-io/claude-plugin/build-sequences"><img src="https://agentmods.dev/badge/skills/hunter-io/claude-plugin/build-sequences/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 build-sequences

Your own site · 80×15
<a href="https://agentmods.dev/skills/hunter-io/claude-plugin/build-sequences"><img src="https://agentmods.dev/badge/skills/hunter-io/claude-plugin/build-sequences.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,207 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00072 $0.02207
Opus 5.5 $0.00029 $0.00883
Sonnet 5.5 $0.00014 $0.00441
Haiku 4.5 $0.00007 $0.00221

Measured 3d ago against content hash 151d7597b04a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

build-sequences 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 3d 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.

skills/build-sequences/SKILL.md · 98 lines

How it starts

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

Build Sequences

Create, configure, and run Hunter email sequences from chat: create the sequence, write the introduction email, add follow-up steps and message templates, add recipients, launch, and read stats. Step authoring never needs the dashboard. Connecting a sending inbox still does — the API only attaches an account that is already connected, so check List-Email-Accounts before promising a fully in-chat launch.

Examples

  • /hunter:build-sequences Set up a 3-step outreach sequence for my fintech leads
  • "Create a sequence called Q2 Outreach with a follow-up after 3 days"
  • "Add the leads from my SaaS list to the Q2 Outreach sequence"
  • "Start the Q2 Outreach sequence"
  • "Pause my running sequence"
  • "How is the Product Launch sequence performing?"

Workflow

Step 1: Identify or create the sequence

  • Existing sequence named or given by ID → call Get-Sequence to load its live status, sender, settings, and recipient count before acting (start/resume/archive/add-recipients should rely on this, not stale list rows). To browse, call List-Sequences.
  • New sequence → call Create-Sequence with a descriptive name. Then configure it (Steps 2–3).
# Your Sequences

| ID | Name | Status | Recipients |
|----|------|--------|------------|
| 123 | Q2 Outreach | draft | 0 |
| 456 | Product Launch | running | 150 |

Step 2: Configure steps and templates

  • Message templates — Create-Message-Template (requires a name and body; subject optional), reusable across sequences. List-Message-Templates to reuse an existing one (Get-Message-Template to inspect); Update-Message-Template to edit.
  • Follow-up steps — Create-Sequence-Follow-Up to append each new step (delay + template). List-Sequence-Follow-Ups to review the cadence (Get-Sequence-Follow-Up for one step). Update-Sequence-Follow-Up rewrites an existing step in place — subject, body, wait_days, or message_format. Two side effects to surface, both Hunter-side and neither undoable from chat: a subject edit also rewrites every later step still holding the old subject verbatim (and regenerates their pending messages on a started sequence) — including steps appended with no subject of their own, which is the normal build order — so always re-read the step list afterwards and report which other steps moved; and switching a step from html to text makes Hunter convert the stored body (images dropped, links flattened, HTML stripped) even if you send no body, so confirm that before doing it. Delete-Sequence-Follow-Up removes a step, but only the last step can be deleted and never step 0, so prefer an update over delete + recreate. A sequence holds at most 6 steps total — the step-0 introduction plus up to 5 follow-ups — so longer drips aren't possible.

Read the full file on GitHub · 98 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. 3d ago Changed · +2 lines 151d7597b04a
  2. 1mo ago Changed · +1 lines f7484f309ebe
  3. 1mo ago First seen · 95 lines · 72 tokens per session scan A f75ab90d1c68

Subscribe to this mod's changes

build-sequences is a skill published in the GitHub repository hunter-io/claude-plugin (8 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 2,207 once invoked, about $0.0003 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-08-30.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 123 tokens