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/tahirraufkeeyu/software-development-agent-stack--sdas/outbound-sequencenpx skills add tahirraufkeeyu/software-development-agent-stack--sdas --skill outbound-sequencegit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/outbound-sequence)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/outbound-sequence"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/outbound-sequence.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.1 | $0.00051 | $0.02426 |
| Opus 5 | $0.00026 | $0.01213 |
| Sonnet 5 | $0.00010 | $0.00485 |
| Haiku 4.5 | $0.00005 | $0.00243 |
Grade A, and why
outbound-sequence 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 6d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Invoke this orchestrator when:
- A rep is preparing to open a net-new account and wants a research-backed sequence ready for review before anything goes out.
- A target account was added to the quarter's top-20 list and needs a full outbound package.
- A triggering signal fired (new exec hire, funding round, tech-stack change) and the team wants a ready-to-ship sequence personalized to that trigger.
- Sales ops is batch-preparing sequences for an upcoming outbound sprint.
Do not use for warm inbound replies (use a lighter follow-up skill), for existing customers (use account-expansion), or when the rep only needs one of the sub-artifacts — call that skill directly.
Chained skills
Four skills run in a fixed order. Research feeds everything downstream, so it must run first. Competitive analysis is conditional on an incumbent being detected.
lead-research— produces a one-page brief: firmographics, tech stack, trigger events, outreach angles, ICP fit score.competitive-analysis— only invoked if research names an incumbent vendor; pulls or writes the battlecard.email-outreach— drafts a 3-touch cold sequence (cold, follow-up, breakup) that cites specific triggers and angles from the brief.meeting-prep— drafts a discovery-call brief assuming the prospect replies: attendees, likely priorities, talking points, landmines, objection handling.
Inputs
account_name— canonical company name (e.g.Acme Retail,Nimbus Logistics). Used for filenames; slugified toacme-retail.rep_persona— the target buyer persona (e.g.platform engineering leader,VP of Data,CIO). Drives tone and angle selection.product_positioning(optional) — one-liner on which of our products to lead with. Defaults to the persona's usual fit.rep_nameandrep_title— used to sign the emails.analyst_notes(optional) — anything the rep already knows that should be respected (e.g. "already met the CTO at re:Invent"). Merged into the research brief.
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.
- 6d ago First seen · 136 lines · 51 tokens per session scan A 324cb318945d
outbound-sequence is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 2,426 once invoked, about $0.0003 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…