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 aAAaqwq/AGI-Super-Team --skill cold-email-sequence-generatorgit clone --depth 1 https://github.com/aAAaqwq/AGI-Super-TeamWrote 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/aaaaqwq/agi-super-team/cold-email-sequence-generator)<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/cold-email-sequence-generator"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/cold-email-sequence-generator/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/aaaaqwq/agi-super-team/cold-email-sequence-generator"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/cold-email-sequence-generator.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.00059 | $0.05033 |
| Opus 5 | $0.00030 | $0.02516 |
| Sonnet 5 | $0.00012 | $0.01007 |
| Haiku 4.5 | $0.00006 | $0.00503 |
Grade A, and why
cold-email-sequence-generator 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.
This is a copy
100% identical to cold-email-sequence-generator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 698 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Email Sequence Generator
Create personalized, high-converting cold email sequences with optimal timing and A/B testing.
Instructions
You are an expert email copywriter specializing in outbound sales sequences that get responses. Your mission is to craft personalized, value-driven email sequences that respect the recipient's time while clearly communicating value.
Core Capabilities
Sequence Types:
- Classic Cold Outreach (7 emails, 2 weeks)
- Fast-Track (5 emails, 1 week)
- Long-Play Nurture (12-14 emails, 4-6 weeks)
- Event/Trigger-Based (3-5 emails, event-specific)
- Re-Engagement (5 emails, revive old leads)
Personalization Levels:
- Hyper-Personal: Unique research for each prospect
- Account-Based: Company-specific messaging
- Segment-Based: Industry/role personalization
- Volume: Template with merge tags
Key Features:
- A/B subject line variations
- Optimal send timing (day/time)
- Follow-up spacing logic
- Social proof integration
- Call-to-action optimization
- Breakup email strategy
- Re-engagement triggers
Email Sequence Framework
Email 1: The Introduction
- Goal: Make them aware you exist
- Focus: Relevant problem + quick win
- Length: 50-100 words
- CTA: Soft ask (reply, quick question)
Email 2: The Value Proof
- Goal: Establish credibility
- Focus: Case study or social proof
- Length: 75-125 words
- CTA: Specific meeting time
Email 3: The Different Angle
- Goal: Address alternative pain point
- Focus: Another use case or benefit
- Length: 50-75 words
- CTA: Yes/no question
Email 4: The Social Proof
- Goal: Show others like them trust you
- Focus: Customer testimonial or stat
- Length: 60-90 words
- CTA: Simple reply
Email 5: The Resource Share
- Goal: Give before asking
- Focus: Helpful content (guide, video)
- Length: 40-60 words
- CTA: Soft (let me know if helpful)
Email 6: The Direct Ask
- Goal: Be straightforward
- Focus: Clear value proposition
- Length: 30-50 words
- CTA: Direct meeting request
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 · 698 lines · 59 tokens per session scan A 89082db5e31f
cold-email-sequence-generator is a skill published in the GitHub repository aAAaqwq/AGI-Super-Team (91 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 5,033 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cold-email-sequence-generator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
deslop
The optimization pass, defined - delete before you add, one smell class per pass, behaviour pinned by a test that ran BEFORE the edit. Lints a SKILL.md and prose by the same instinct. Use for the per-story optimization pass or when code has grown noisy without growing capable.
root-cause
Find the mechanism behind a failure instead of patching its symptom - reproduce first, one variable per experiment with the prediction written before the run, exit by naming the mechanism and pinning it with a failing test. Use for a bug, an unexplained red test, or a failure that will not reproduce.
guidance
Add, edit, or audit guidance docs. Default writes guidance for Claude (.claude/guidance/, Markdown, moflo universal rules). -h writes for human readers (docs/, lighter ruleset). --html emits HTML with a minimal default stylesheet instead of Markdown. -a audits the .claude/guidance/ directory.
eldar
Consult the Eldar — audit a project's moflo + Claude Code setup for portable, high-leverage gaps and guide remediation. Default mode is read-only audit with severity-ranked findings; --fix presents an interactive triage menu and walks the user through each chosen fix (healer, missing CLAUDE.md, sparse guidance…
aigon-next
Suggest the most likely next workflow action based on current context.
review-deep
Drive the deep-review phase of an automated PR review. Consumes the walkthrough, runs the deterministic deep-review workflow (parallel lenses → adversarial validation → code-enforced threshold/caps), drafts the surviving findings, and completes the review run.