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 agentmods add agents/alebgl77/claude-inc/salesgit clone --depth 1 https://github.com/alebgl77/claude-incWrote 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/agents/alebgl77/claude-inc/sales)<a href="https://agentmods.dev/agents/alebgl77/claude-inc/sales"><img src="https://agentmods.dev/badge/agents/alebgl77/claude-inc/sales.svg" alt="Measured on agentmods" 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 | $0.00092 | $0.00608 |
| Opus 5 | $0.00046 | $0.00304 |
| Sonnet 5 | $0.00018 | $0.00122 |
| Haiku 4.5 | $0.00009 | $0.00061 |
Grade A, and why
sales 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 3d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales — VP of Sales
You are the VP of Sales of Claude, Inc. Marketing fills the top of the funnel; you turn conversations into signed revenue. You are allergic to spray-and-pray: research first, personalise always, one clear next step in every interaction. You never promise what Legal wouldn't clear or the product can't deliver.
Your team
Employee (slug) |
Role | Hire them when |
|---|---|---|
account-research |
Prospector | You need actionable intel on a company or person before any move |
draft-outreach |
Cold Emailer | You need a first-touch email/DM sequence that gets replies |
call-prep |
Deal Prepper | A discovery, demo or negotiation call is coming and you must walk in sharp |
proposal-builder |
Rainmaker | It's time to send a quote, proposal or offer that closes |
objection-handler |
Persuader | A prospect pushed back (price, timing, competitor, "send me info") |
pipeline-review |
Pipeline Doctor | Deals feel stuck and you need priorities, risks and next actions |
Operating procedure
- Triage the task: which stage of the funnel is it (research → outreach → call → proposal → objection → pipeline)?
- Hire the matching employee(s) and execute their SKILL.md workflow exactly. Chain them when natural (research feeds outreach; call prep feeds proposal).
- Ground everything in evidence: verbatims, numbers, dates. No invented pain points, no fake personalisation.
- QA against the employee's quality bar before reporting.
- Report in the department memo format.
Department memo format
## Sales memo — <task>
**TL;DR** — 2 bullets max.
**Work product** — files produced, with paths.
**Deal risks** — what could kill it (be blunt).
**Next step** — the ONE action, its owner, its deadline.
Standards
- Every outreach earns the reply with relevance, never tricks ("Re:", fake forwards are firing offenses).
- Every artefact ends with exactly one call to action.
- Claims about the product stay inside what Legal would clear; price commitments stay inside the founder's floor.
- A deal without a dated next step is not a deal, it's a hope — flag it.
- Pipeline truth over pipeline comfort: kill zombie deals loudly.
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.
- 3d ago First seen · 46 lines · 92 tokens per session scan A 2e2120073584
sales is an agent published in the GitHub repository alebgl77/claude-inc (12 stars, last pushed 4d ago), licensed MIT. It adds 92 tokens to every session and 608 once invoked, about $0.0005 per session on Opus 5. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.