Borrowing it
Nothing to install: this file belongs to Othmane-Khadri/gtm-engineer-playbook. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Othmane-Khadri/gtm-engineer-playbook/main/.claude/skills/gtm-playbook/outreach-sequence-builder/SKILL.mdgit clone --depth 1 https://github.com/Othmane-Khadri/gtm-engineer-playbookWrote 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/othmane-khadri/gtm-engineer-playbook/outreach-sequence-builder)<a href="https://agentmods.dev/skills/othmane-khadri/gtm-engineer-playbook/outreach-sequence-builder"><img src="https://agentmods.dev/badge/skills/othmane-khadri/gtm-engineer-playbook/outreach-sequence-builder/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/othmane-khadri/gtm-engineer-playbook/outreach-sequence-builder"><img src="https://agentmods.dev/badge/skills/othmane-khadri/gtm-engineer-playbook/outreach-sequence-builder.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.00077 | $0.03136 |
| Opus 5 | $0.00039 | $0.01568 |
| Sonnet 5 | $0.00015 | $0.00627 |
| Haiku 4.5 | $0.00008 | $0.00314 |
Grade A, and why
outreach-sequence-builder 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.
How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outreach Sequence Builder
Build signal-triggered, multi-channel outreach sequences that convert. Maps Signal --> Angle --> Channel --> Message --> Objection Pre-emption. Produces ready-to-use sequences in markdown, written to docs/sequences/.
Can reference docs/icp.md for persona and pain-point data, and docs/accounts/*.md for account-level personalization. Works for any B2B product or service.
Methodology
Follow these steps in order. Do not skip steps. Do not produce output until Step 7.
Step 1 -- Context Loading
Check for existing files before asking questions.
-
Read
docs/icp.mdif it exists. Extract:- Target personas (titles, seniority, department)
- Company profile (size, industry, stage)
- Pain points (ranked by severity)
- Language patterns (how prospects describe their problems in their own words)
- Key differentiators of the product/service
-
Glob
docs/accounts/*.mdif any exist. Extract:- Account names and context
- Known tech stack, recent news, or specific pain points
- Any existing relationship context
-
If neither file exists, gather the minimum viable context by asking the user these four questions (all four are required before proceeding):
- What does your product/service do? (one paragraph)
- Who are you targeting? (job title, company size, industry)
- What is the main problem you solve? (from the buyer's perspective)
- What is your key differentiator? (why you over the alternative)
Do not proceed to Step 2 until context is loaded or gathered.
Step 2 -- Trigger Selection
Present the trigger signal menu and ask the user to select one or more:
| # | Trigger Signal | Example |
|---|---|---|
| 1 | Post-Fundraise | Company just raised a round -- they have budget and a mandate to grow |
| 2 | Hiring Signal | Company posting SDR, GTM, growth, or ops roles -- they are scaling a function you serve |
| 3 | Competitor Displacement | Prospect is using a competitor and showing frustration -- switching cost feels low |
| 4 | Product Launch | Company released a new product or feature -- adjacent needs surface |
| 5 | Content Engagement | Prospect liked, commented, or shared content relevant to your space |
| 6 | Event Follow-up | Met at a conference, attended the same webinar, or appeared on the same panel |
| 7 | Job Change | Contact moved to a new company -- fresh mandate, open to new vendors |
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 · 276 lines · 77 tokens per session scan A 6057738d6670
outreach-sequence-builder is a skill published in the GitHub repository Othmane-Khadri/gtm-engineer-playbook (56 stars, last pushed 5mo ago), licensed MIT. It adds 77 tokens to every session and 3,136 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
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
adoption-leaderboard
Scores a rep's or a team's recent sales calls against a fixed set of five winning-behavior checklists (rapport, upsell signals, renewal risk, customer experience, value realization), then ranks reps lowest-adoption-first so the highest-leverage coaching targets lead. Use when running a team calibration, prepping 1:1…
challenger
Audits a B2B sales call transcript against the Challenger Sale framework (teach, tailor, take control, plus the commercial-teaching pitch arc), or sweeps a CRM export for deals with no teaching insight logged. Use when a rep leans on discovery-question skill but rarely brings a point of view, when prepping a rep for a…
meddpicc
Audits a B2B sales call transcript against the MEDDPICC qualification framework (Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition), or sweeps a CRM export for deals missing MEDDPICC fields. Use when a deal is heading toward legal/procurement/security…
persona-based-discovery
Audits whether a discovery call's questions and framing were actually tailored to the specific buyer persona in the room (technical evaluator, economic buyer, end user, etc.), or sweeps a CRM export for deals with no persona/role data attached to contacts. Use when checking that a rep adapted to who they were talking…
sandler
Audits a B2B sales call transcript against the Sandler Selling System submarine (Bonding & Rapport, Up-Front Contract, Pain, Budget, Decision, Fulfillment, Post-Sell), or sweeps a CRM export for deals missing Sandler-relevant fields. Use when checking whether a rep pitched before earning the right to, whether a close…