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 skills add Doris-Labs/sales-skills --skill sequence-writinggit clone --depth 1 https://github.com/Doris-Labs/sales-skillsWrote 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/doris-labs/sales-skills/sequence-writing)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/sequence-writing"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/sequence-writing/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/doris-labs/sales-skills/sequence-writing"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/sequence-writing.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.00072 | $0.01398 |
| Opus 5 | $0.00036 | $0.00699 |
| Sonnet 5 | $0.00014 | $0.00280 |
| Haiku 4.5 | $0.00007 | $0.00140 |
Grade A, and why
sequence-writing 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 10d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sequence Writing
Purpose
Turn a target persona and a reason-to-reach-out into a complete multi-touch cadence: the right channel mix, the right spacing, a different angle on every touch, and a breakup that creates urgency — so the prospect hears a campaign, not eight copies of the same email.
Inputs
- Who you're reaching (persona, role, company, segment)
- The trigger or reason to reach out (event, pain, mutual deal context)
- Channels available (email, phone, LinkedIn) and how aggressive the motion can be
- Any known personalization hooks (recent meeting, prior deal, shared connection)
Method
A sequence is a story told across touches. The unit of design is the touch — each one has a channel, a time, and a single angle. Two rules govern the whole thing.
The value-per-touch rule: every touch must add something the prospect didn't have before — a new insight, a different proof point, a relevant resource, a question they haven't been asked. "Just bumping this" / "circling back" / "did you see my email" are not touches; they are noise that trains the prospect to ignore you. If a touch has no new angle, delete it.
Channel mix: alternate channels so you're not a single muted inbox thread. Email carries the substance; phone creates a live moment; LinkedIn warms and humanizes. A multi-threaded prospect who has seen you in three places replies more than one hit eight times in the same place.
Concrete cadence (8 touches over ~18 business days):
| # | Day | Channel | Angle |
|---|---|---|---|
| 1 | Day 1 | Trigger + one specific hypothesis about their pain. One ask. | |
| 2 | Day 1 | Connection request, no pitch — reference the trigger in the note. | |
| 3 | Day 3 | Call + voicemail | Reference touch 1; leave a 20-sec voicemail, then email "tried to reach you." |
| 4 | Day 5 | New angle: a proof point / peer result relevant to their segment. | |
| 5 | Day 8 | Share or comment with a relevant resource (article, data point). | |
| 6 | Day 11 | Call + voicemail | Different pain angle; voicemail naming a peer outcome. |
| 7 | Day 14 | Pattern-interrupt: short, one provocative question tied to their world. | |
| 8 | Day 18 | Breakup email (see below). |
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.
- 10d ago First seen · 113 lines · 72 tokens per session scan A 5d13fca448bc
sequence-writing is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 1,398 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-31.
Other skills, from other repositories
lynqu
Entry point for the Lynqu sales suite — describe any sales situation and it composes the right skills across capture, outreach, quoting and reporting. Requires the Lynqu MCP server connected.
lynqu-sales-playbook
Turn a written sales playbook into a live Lynqu pipeline — contacts, timed tasks, follow-up templates, the playbook attached to each lead, and stage rules that deliver the prep at the right moment.
lynqu-card-studio
Create and update Lynqu digital business cards — contact info, social links, services, template, palette — and check card views, scans and shares. Requires the Lynqu MCP server connected.
lynqu-competitors
Build a battlecard for the incumbent on a Lynqu deal — switching cost, wedge, objections and honest answers — written back to the lead. Requires the Lynqu MCP server.
lynqu-contacts
Map the buying committee on an account — economic buyer, champion, blocker — and write it into Lynqu as contacts and participants. Requires the Lynqu MCP server.
lynqu-deal-desk
Price a Lynqu deal and draft the quote — browse the price book, put priced lines on a deal, then produce a draft quote for a human to send. Requires the Lynqu MCP server connected.