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/apolloio/apollo-mcp-plugin/sequence-loadnpx skills add apolloio/apollo-mcp-plugin --skill sequence-loadgit clone --depth 1 https://github.com/apolloio/apollo-mcp-pluginWhat 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.00033 | $0.01024 |
| Opus 5 | $0.00016 | $0.00512 |
| Sonnet 5 | $0.00007 | $0.00205 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
sequence-load 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sequence-load — 88% identical, 45 lines differ
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sequence Load
Find, enrich, and load contacts into an outreach sequence — end to end. The user provides targeting criteria and a sequence name via "$ARGUMENTS".
Examples
/apollo:sequence-load add 20 VP Sales at SaaS companies to my "Q1 Outbound" sequence/apollo:sequence-load SDR managers at fintech startups → Cold Outreach v2/apollo:sequence-load list sequences(shows all available sequences)/apollo:sequence-load directors of engineering, 500+ employees, US → Demo Follow-up/apollo:sequence-load reload 15 more leads into "Enterprise Pipeline"
Step 1 — Parse Input
From "$ARGUMENTS", extract:
Targeting criteria:
- Job titles →
person_titles - Seniority levels →
person_seniorities - Industry keywords →
q_organization_keyword_tags - Company size →
organization_num_employees_ranges - Locations →
person_locationsororganization_locations
Sequence info:
- Sequence name (text after "to", "into", or "→")
- Volume — how many contacts to add (default: 10 if not specified)
If the user just says "list sequences", skip to Step 2 and show all available sequences.
Step 2 — Find the Sequence
Use mcp__claude_ai_Apollo_MCP__apollo_emailer_campaigns_search to find the target sequence:
- Set
q_nameto the sequence name from input
If no match or multiple matches:
- Show all available sequences in a table: | Name | ID | Status |
- Ask the user to pick one
Step 3 — Get Email Account
Use mcp__claude_ai_Apollo_MCP__apollo_email_accounts_index to list linked email accounts.
- If one account → use automatically
- If multiple → show them and ask which to send from
Step 4 — Find Matching People
Use mcp__claude_ai_Apollo_MCP__apollo_mixed_people_api_search with the targeting criteria.
- Set
per_pageto the requested volume (or 10 by default)
Present the candidates in a preview table:
| # | Name | Title | Company | Location |
|---|
Ask: "Add these [N] contacts to [Sequence Name]? This will consume [N] Apollo credits for enrichment."
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 · 121 lines · 33 tokens per session scan A ae2c2377cc3c
sequence-load is a skill published in the GitHub repository apolloio/apollo-mcp-plugin (19 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,024 once invoked, about $0.0002 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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
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…