sales-research

sales-research is a skill for Claude Code, Codex from zubair-trabzada/ai-sales-team-claude. It costs 0 tokens per session (4,726 once invoked), scanned A, original, MIT.

A company-research task for examining a potential customer across eight research areas, using its website and other specified sources. It can run on its own or as part of a larger prospect audit.

In plain words
What is it for?
Use it to research a company’s products, positioning, history, team, locations, and other business details, then produce company research for sales qualification.
Why use it?
It saves sales teams from manually gathering company facts across many pages and sources. It organizes the findings into a structured company report and fit score.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; positional $N argument.

Good fit Use it to research a company’s products, positioning, history, team, locations, and other business details, then produce company research for sales qualification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zubair-trabzada/ai-sales-team-claude/sales-research
About the project

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.

zubair-trabzada/ai-sales-team-claude · 1,143 stars · on GitHub · skool.com

Install

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.

Any agent
npx skills add zubair-trabzada/ai-sales-team-claude --skill sales-research
Clone the repo
git clone --depth 1 https://github.com/zubair-trabzada/ai-sales-team-claude

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for sales-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/zubair-trabzada/ai-sales-team-claude/sales-research/github.svg)](https://agentmods.dev/skills/zubair-trabzada/ai-sales-team-claude/sales-research)
Your own site
<a href="https://agentmods.dev/skills/zubair-trabzada/ai-sales-team-claude/sales-research"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/ai-sales-team-claude/sales-research/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.

agentmods 80×15 button for sales-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/zubair-trabzada/ai-sales-team-claude/sales-research"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/ai-sales-team-claude/sales-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,726 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.04726
Opus 5 $0.00000 $0.02363
Sonnet 5 $0.00000 $0.00945
Haiku 4.5 $0.00000 $0.00473

Measured 13d ago against content hash ee7aebad8e92, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sales-research 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.

skills/sales-research/SKILL.md · 476 lines

How it starts

The opening of the file, as written. The whole thing — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Company Research & Firmographic Analysis

You are the company research engine for /sales research <url>. You produce deep, structured intelligence on a prospect company covering 8 research dimensions. This skill is invoked standalone or as the sales-company subagent within /sales prospect.

When This Skill Is Invoked

  • Standalone: The user runs /sales research <url>. Perform the full research procedure and output COMPANY-RESEARCH.md.
  • As subagent: The sales-prospect orchestrator launches this skill as the sales-company subagent. You receive a discovery briefing with pre-fetched page content. Use it to skip redundant fetches. Return a Company Fit Score (0-100) with structured data.

Phase 1: Website Analysis (Primary Source)

1.1 Fetch and Analyze Key Pages

Use WebFetch to retrieve these pages (skip any already provided in the discovery briefing):

Page Common URLs Priority Data
Homepage / Company name, tagline, value prop, product positioning, social proof
About /about, /company, /about-us, /our-story Founding story, mission, vision, values, team size, locations, history
Team /team, /leadership, /about/team, /people Executive names, titles, backgrounds, advisory board
Pricing /pricing, /plans, /packages Revenue model, price points, tier structure, enterprise tier
Blog /blog, /resources, /insights Content themes, posting frequency, thought leadership quality
Careers /careers, /jobs, /join-us, /open-positions Open roles, team sizes, growth rate, culture signals, tech stack
Customers /customers, /case-studies Customer logos, industries served, company sizes served
Press /press, /news, /newsroom Recent announcements, media coverage, partnerships
Legal /privacy, /terms Legal entity name, jurisdiction, compliance standards

1.2 Technology Stack Detection

Identify technologies used by the prospect from these signals:

Read the full file on GitHub · 476 lines

Changes

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.

  1. 13d ago First seen · 476 lines · 0 tokens per session scan A ee7aebad8e92

Subscribe to this mod's changes

sales-research 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,726 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens