AI Sales Team for Claude Code is a command-line sales workflow that uses Claude Code to research companies, assess leads, identify decision makers, create outreach and follow-up sequences, prepare meetings, draft proposals, and generate pipeline reports. Sales and business-development users employ its commands and parallel agents to turn prospect information into research and sales materials. The catalogue entries are the workflow’s bundled skills and agents.
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 zubair-trabzada/ai-sales-team-claude --skill sales-followupgit clone --depth 1 https://github.com/zubair-trabzada/ai-sales-team-claudeWrote 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/zubair-trabzada/ai-sales-team-claude/sales-followup)<a href="https://agentmods.dev/skills/zubair-trabzada/ai-sales-team-claude/sales-followup"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/ai-sales-team-claude/sales-followup/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/zubair-trabzada/ai-sales-team-claude/sales-followup"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/ai-sales-team-claude/sales-followup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 407 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00000 | $0.04761 |
| Opus 5.5 | $0.00000 | $0.01904 |
| Sonnet 5.5 | $0.00000 | $0.00952 |
| Haiku 4.5 | $0.00000 | $0.00476 |
Grade A, and why
sales-followup 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 2mo 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 — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follow-Up Sequence Generator
You generate strategic follow-up email sequences for prospects after initial contact has been made. This is NOT cold outreach — these are follow-ups after a meeting, demo, proposal, or prior conversation. Every follow-up must add new value, reference specific conversation points, and include a clear next step.
Invocation
/sales followup <prospect>
Where <prospect> is a company name, contact name, URL, or description of the prospect and the follow-up context.
Step 1: Gather Follow-Up Context
Before generating any sequence, collect the following information. If not provided, ask the user:
- Prospect name and company
- Previous interaction type: Meeting, Demo, Proposal, Went Silent (Ghost), or Long-Term Nurture
- Date of last interaction
- Key discussion points from the last interaction (at least 3 specifics)
- Prospect's stated pain points or goals
- Next step that was agreed upon (if any)
- Prospect's role and seniority level (affects tone and content)
- Deal stage: Early exploration, Active evaluation, Near decision, Stalled
- Prospect temperature: Hot (actively engaged), Warm (interested but slow), Cool (disengaged), Cold (ghosted)
- Your product/service and the specific solution discussed
If previous analysis files exist in the working directory (PROSPECT-ANALYSIS.md, COMPANY-RESEARCH.md, LEAD-QUALIFICATION.md, DECISION-MAKERS.md, OUTREACH-SEQUENCE.md), read them and automatically incorporate relevant findings into the follow-up context.
Step 2: Select Follow-Up Scenario
Based on the previous interaction type, select the matching scenario from below. If the user does not specify, ask which scenario fits best.
Scenario 1: Post-Meeting Follow-Up (3 Emails)
Use this when: A discovery call, introductory meeting, or strategy session has taken place.
Email 1 — Summary + Next Steps (Send: Same day, within 2 hours of meeting)
- Subject line format: Use the meeting topic or a key takeaway, not "Great meeting today"
- Open with ONE specific insight or moment from the meeting that stood out (shows you were listening)
- Summarize the 3 key points discussed in bullet form
- Restate the agreed-upon next step with a specific date and time
- Attach or link any materials promised during the meeting
- Close with a confirmation question: "Does this accurately capture what we discussed?"
- Length: 80-100 words
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.
- 2mo ago First seen · 408 lines · 0 tokens per session scan A f4322dbb2a80
sales-followup is a skill published in the GitHub repository zubair-trabzada/ai-sales-team-claude (1,508 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,761 tokens. 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.
sales-followup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sales-followupzubair-trabzada/ai-sales-team-claude | Skill | 1.5k | 7mo ago | MIT | A | 0 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 103 | Claude Code |