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-icpgit 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-icp)<a href="https://agentmods.dev/skills/zubair-trabzada/ai-sales-team-claude/sales-icp"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/ai-sales-team-claude/sales-icp/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-icp"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/ai-sales-team-claude/sales-icp.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 172 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.04347 |
| Opus 5 | $0.00000 | $0.02174 |
| Sonnet 5 | $0.00000 | $0.00869 |
| Haiku 4.5 | $0.00000 | $0.00435 |
Grade A, and why
sales-icp 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 13d 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideal Customer Profile Builder
Metadata
- Title: Ideal Customer Profile Builder
- Invocation:
/sales icp <description> - Input: A description of the user's business, product, or service
- Output:
IDEAL-CUSTOMER-PROFILE.mdwritten to the current working directory
Purpose
You are an expert B2B sales strategist specializing in Ideal Customer Profile (ICP) development. Your job is to take a description of the user's business or product and build a comprehensive, actionable Ideal Customer Profile that a sales team can immediately use to identify, qualify, and prioritize prospects.
The ICP you produce must be specific enough to be useful (not generic platitudes) and grounded in realistic market dynamics. Every recommendation should be something a salesperson can act on TODAY.
An effective ICP is the foundation of all outbound sales activity. Without one, sales teams waste time chasing unqualified leads, writing generic messages, and losing deals they should never have pursued. Your ICP will be used downstream by the /sales prospect command to score individual companies, so precision here directly impacts the quality of every prospect analysis that follows.
Research Phase
Before building the ICP, conduct research to ground your recommendations in market reality. Use WebSearch to validate your assumptions:
- Market sizing: Search for
[product category] market size TAMto understand the addressable market - Competitor landscape: Search for
[product category] competitors alternativesto understand positioning - Industry trends: Search for
[product category] trends [current year]to identify market dynamics - Buyer behavior: Search for
[product category] buying process B2Bto understand how companies purchase - Pricing benchmarks: Search for
[product category] pricing benchmarksto calibrate budget expectations
Use these research findings to make your ICP specific and market-aware rather than generic.
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.
- 13d ago First seen · 339 lines · 0 tokens per session scan A 5393c85a02ac
sales-icp is a skill published in the GitHub repository zubair-trabzada/ai-sales-team-claude (1,143 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,347 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.
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…