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-competitorsgit 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-competitors)<a href="https://agentmods.dev/skills/zubair-trabzada/ai-sales-team-claude/sales-competitors"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/ai-sales-team-claude/sales-competitors/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-competitors"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/ai-sales-team-claude/sales-competitors.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.03994 |
| Opus 5 | $0.00000 | $0.01997 |
| Sonnet 5 | $0.00000 | $0.00799 |
| Haiku 4.5 | $0.00000 | $0.00399 |
Grade A, and why
sales-competitors 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 — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Competitive Intelligence
You analyze what tools, services, and solutions a prospect currently uses and generate actionable battle cards for selling against each detected competitor. This is NOT a general market analysis — it is focused entirely on helping a salesperson WIN a deal against specific competitors that a specific prospect is currently using or evaluating.
Invocation
/sales competitors <url>
Where <url> is the prospect company's website URL. The skill detects what the prospect currently uses and builds sales-focused battle cards for each detected solution.
Step 1: Current Solution Detection
Execute all of the following detection methods in parallel using WebFetch and WebSearch. The goal is to identify every tool, service, platform, and vendor the prospect currently relies on that overlaps with or is adjacent to your offering.
1.1 Website Technology Analysis
Fetch the prospect's website and analyze:
- HTML source inspection: Look for script tags, meta tags, and link tags that reference known tools and platforms (e.g., analytics tools, CRM embeds, chat widgets, marketing automation pixels, tag managers, CDN providers)
- Integration badges and partner logos: Check the homepage, footer, integrations page, and partners page for logos of tools they use or integrate with
- "Powered by" footers: Many SaaS tools place a small badge or link in the footer of pages they power (e.g., help desks, landing pages, e-commerce platforms)
- Technology stack signals: Identify the website platform (WordPress, Webflow, Shopify, custom), hosting provider, CDN, email service provider, and other infrastructure choices
- Login/portal pages: Check for links to internal tools (e.g., "Login to Dashboard" that redirects to a known SaaS platform)
- API documentation: If they have a developer/API page, check what integrations they document — this reveals their stack
Record each detected technology with:
- Tool/platform name
- Evidence source (URL, page element, or signal that revealed it)
- Confidence level: High (explicit mention or badge), Medium (script tag or indirect reference), Low (inference from job posting or industry norm)
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 · 402 lines · 0 tokens per session scan A 32ddccb7c5f4
sales-competitors 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 3,994 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…