sales-enablement

sales-enablement is a skill for Claude Code from shalintripathi/saas-marketing-agents. It costs 599 tokens per session (6,341 once invoked), scanned A, original, MIT.

A sales-enablement toolkit for B2B SaaS revenue teams, including technical presales work such as demos, proposals, RFP responses, and pilots.

In plain words
What is it for?
Use it to plan outbound campaigns, run discovery calls, build battle cards, write proposals, answer RFPs, prepare demos, and scope proofs of concept.
Why use it?
It helps sales and technical teams prepare consistent materials and handle complex deals from first discovery through evaluation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the saas-marketing plugin — 19 skills, 91 agents shipped together

Good fit Use it to plan outbound campaigns, run discovery calls, build battle cards, write proposals, answer RFPs, prepare demos, and scope proofs of concept.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/shalintripathi/saas-marketing-agents/sales-enablement
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 shalintripathi/saas-marketing-agents --skill sales-enablement
Clone the repo
git clone --depth 1 https://github.com/shalintripathi/saas-marketing-agents

Made for: Claude Code.

Or install saas-marketing, the plugin that ships this one along with the rest of its 19 skills, 91 agents.

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-enablement

README.md
[![agentmods](https://agentmods.dev/badge/skills/shalintripathi/saas-marketing-agents/sales-enablement/github.svg)](https://agentmods.dev/skills/shalintripathi/saas-marketing-agents/sales-enablement)
Your own site
<a href="https://agentmods.dev/skills/shalintripathi/saas-marketing-agents/sales-enablement"><img src="https://agentmods.dev/badge/skills/shalintripathi/saas-marketing-agents/sales-enablement/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-enablement

Your own site · 80×15
<a href="https://agentmods.dev/skills/shalintripathi/saas-marketing-agents/sales-enablement"><img src="https://agentmods.dev/badge/skills/shalintripathi/saas-marketing-agents/sales-enablement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 599 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,341 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.
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.00599 $0.06341
Opus 5.5 $0.00240 $0.02536
Sonnet 5.5 $0.00120 $0.01268
Haiku 4.5 $0.00060 $0.00634

Measured 3d ago against content hash 15b1ad40d53a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/saas-marketing/skills/sales-enablement/SKILL.md · 391 lines

How it starts

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

Sales Enablement

Step 0 (always first): Load brand context

Before producing any deliverable, look for a brand-context.md file in the user's project root (also check ./.claude/brand-context.md and ./docs/brand-context.md). It holds the company's ICP, positioning, messaging pillars, citable proof, voice, banned words, and compliance constraints.

  • If it exists: read it in full and treat it as binding for this run. Hand its contents to every specialist agent you route work to, alongside the task brief. Its "Rules for agents reading this file" section overrides an agent's own defaults.
  • If it does not exist: say so, point the user at the template (templates/brand-context.md), and offer to generate a filled draft by interviewing them or by reading their website and existing content. Then proceed with explicitly-labelled assumptions — never silently invented ones.

Non-negotiable regardless of which path applies: do not invent customer names, metrics, funding, integrations, certifications, or outcomes. Only proof recorded in brand-context.md (or supplied directly in the request) may be used as fact. Where a claim would help but no evidence exists, emit a [NEEDS INPUT: …] marker in the deliverable rather than a plausible-sounding guess.


What This Is

Sales Enablement brings together sales strategists, discovery coaches, outbound specialists, pipeline analysts, proposal architects, solutions engineers, a conversational agent strategist, and enablement content creators to accelerate deal velocity and maximize win rates. This skill orchestrates your revenue team to execute high-impact outbound campaigns, run disciplined discovery conversations, build data-driven deal strategies, and create compelling proposals that win competitive deals. Whether you're prospecting net-new accounts, accelerating stalled deals, gating a demo, running a proof of concept, answering a vendor security review, building sales battle cards, or executing sales sequences, Sales Enablement routes your request to the right specialist and ensures consistent pipeline progression.

Read the full file on GitHub · 391 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. 3d ago Changed · +1 lines · +47 tokens per session 15b1ad40d53a
  2. 16d ago Changed · +23 tokens per session 87e6ea3e9b80
  3. 17d ago Changed · +1 lines · +57 tokens per session 5464fb0b5e77
  4. 27d ago Changed · +34 tokens per session 112f3988099c
  5. 1mo ago Changed · +4 lines · +128 tokens per session 1eefb76a05e6
  6. 1mo ago Changed · +8 lines · +96 tokens per session 13a5a8876330
  7. 1mo ago First seen · 377 lines · 214 tokens per session scan A 75495c60b0df

Subscribe to this mod's changes

sales-enablement is a skill published in the GitHub repository shalintripathi/saas-marketing-agents (30 stars, last pushed yesterday), licensed MIT. It adds 599 tokens to every session and 6,341 once invoked, about $0.0024 per session on Opus 5.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-09-04.