build-sequences

build-sequences is a skill for Claude Code, Codex from hunter-io/claude-plugin. It costs 72 tokens per session (1,677 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 CodeCodex

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

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.

agentmods
npx agentmods add skills/hunter-io/claude-plugin/build-sequences
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, Codex.

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.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.svg" alt="Measured on agentmods" 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 1,677 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00072 $0.01677
Opus 5 $0.00036 $0.00839
Sonnet 5 $0.00014 $0.00335
Haiku 4.5 $0.00007 $0.00168

Measured 4d ago against content hash f75ab90d1c68, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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 · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 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, add follow-up steps and message templates, add recipients, launch, and read stats. One current limitation: the sequence's introduction email (step 0) has no API yet, so its subject and body must be written once in the Hunter dashboard before the sequence can start.

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 templatesCreate-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 stepsCreate-Sequence-Follow-Up to add each step (delay + template). List-Sequence-Follow-Ups to review the cadence (Get-Sequence-Follow-Up for one step); Delete-Sequence-Follow-Up removes a step, but only the last step can be deleted — to change an earlier one, delete from the end back down to it and recreate the rest (confirm first). 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 · 95 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. 4d 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 (9 stars, last pushed 2d ago), licensed MIT. It adds 72 tokens to every session and 1,677 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 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