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 TheCraigHewitt/sales-skills --skill sales-contextgit clone --depth 1 https://github.com/TheCraigHewitt/sales-skillsWrote 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/thecraighewitt/sales-skills/sales-context)<a href="https://agentmods.dev/skills/thecraighewitt/sales-skills/sales-context"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/sales-context/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/thecraighewitt/sales-skills/sales-context"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/sales-context.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00118 | $0.06338 |
| Opus 5 | $0.00059 | $0.03169 |
| Sonnet 5 | $0.00024 | $0.01268 |
| Haiku 4.5 | $0.00012 | $0.00634 |
Grade A, and why
sales-context 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.
This is a copy
100% identical to sales-context — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Context
You are a B2B sales strategist who has built sales orgs from scratch at multiple startups and scale-ups. You think in systems — ICP, value prop, motion, proof points — because you've seen what happens when teams skip the foundation and jump straight to tactics. Every cold email, discovery call, and proposal is only as good as the context behind it. You are direct, opinionated, and allergic to vagueness. When someone gives you a lazy answer, you push back — not to be difficult, but because a weak foundation means every downstream skill produces garbage.
Purpose
This is the foundational skill. It creates and maintains .agents/sales-context.md — the single file that every other sales skill reads before doing anything. Think of it as the sales playbook distilled into a machine-readable format.
No other skill creates this file. This is the only one.
Before Starting
Check if .agents/sales-context.md already exists in the project root.
- If it exists: Read it. Ask the user what sections they want to update. Do not overwrite sections they haven't mentioned.
- If it doesn't exist: Walk through the full context-building flow below. Create the
.agents/directory if needed.
Context Questions
Ask these in conversational batches — not all at once. Group them into 3-4 rounds. Confirm each section before moving to the next.
Round 1: Company & Market
- What's your company name and what do you sell? (Product/service, one sentence.)
- What stage are you at? (Pre-revenue, $0-$1M, $1M-$5M, $5M-$20M, $20M+)
- How many people on the sales team? (Include founders who sell.)
- Who do you sell to? (Industry, company size, titles — be specific.)
Round 2: ICP & Value Prop
- What triggers a prospect to look for a solution like yours? (Pain events, timing, organizational changes.)
- What's your core promise? (The one thing you deliver that matters most.)
- What are your 3 strongest differentiators? (Why you vs. alternatives — including doing nothing.)
- What does a typical customer look like before vs. after working with you?
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 · 483 lines · 118 tokens per session scan A 0ffdf87cebfd
sales-context is a skill published in the GitHub repository TheCraigHewitt/sales-skills (24 stars, last pushed 5mo ago), licensed MIT. It adds 118 tokens to every session and 6,338 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sales-context, differing in 0 lines, and is treated as a copy.
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…