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 skills/hunter-io/claude-plugin/build-sequencesnpx skills add hunter-io/claude-plugin --skill build-sequencesgit clone --depth 1 https://github.com/hunter-io/claude-pluginWrote 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/hunter-io/claude-plugin/build-sequences)<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>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.00072 | $0.01677 |
| Opus 5 | $0.00036 | $0.00839 |
| Sonnet 5 | $0.00014 | $0.00335 |
| Haiku 4.5 | $0.00007 | $0.00168 |
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.
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-Sequenceto 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, callList-Sequences. - New sequence → call
Create-Sequencewith 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 anameandbody;subjectoptional), reusable across sequences.List-Message-Templatesto reuse an existing one (Get-Message-Templateto inspect);Update-Message-Templateto edit. - Follow-up steps —
Create-Sequence-Follow-Upto add each step (delay + template).List-Sequence-Follow-Upsto review the cadence (Get-Sequence-Follow-Upfor one step);Delete-Sequence-Follow-Upremoves 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.
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.
- 4d ago First seen · 95 lines · 72 tokens per session scan A f75ab90d1c68
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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…