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 rajitsaha/100xprism --skill sales-enablementgit clone --depth 1 https://github.com/rajitsaha/100xprismWrote 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/rajitsaha/100xprism/sales-enablement)<a href="https://agentmods.dev/skills/rajitsaha/100xprism/sales-enablement"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/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.
<a href="https://agentmods.dev/skills/rajitsaha/100xprism/sales-enablement"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/sales-enablement.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.00087 | $0.03074 |
| Opus 5 | $0.00044 | $0.01537 |
| Sonnet 5 | $0.00017 | $0.00615 |
| Haiku 4.5 | $0.00009 | $0.00307 |
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 12d 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
88% identical to sales-enablement — 102 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Enablement
Create B2B sales collateral reps actually use — decks, one-pagers, objection docs, demo scripts, and playbooks that help close deals.
Before Starting
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
Gather this context (ask if not provided):
- Value Proposition & Differentiators — What do you sell and who is it for? What makes you different from the next best alternative? What outcomes can you prove?
- Sales Motion — How do you sell (self-serve, inside sales, field sales, hybrid)? Average deal size and cycle length? Key personas in the buying decision?
- Collateral Needs — What specific assets, for what funnel stage, used by whom (AE, SDR, champion, prospect)?
- Current State — What materials exist, what's working and what's not, what do reps ask for most?
Core Principles
Sales Uses What Sales Trusts
Involve reps in creation and use their language, not marketing's. If reps rewrite your deck before sending it, you wrote the wrong deck. Test drafts with top performers first.
Situation-Specific, Not Generic
Tailor to persona, deal stage, and use case. A CTO deck differs from a VP of Sales deck; a post-meeting one-pager differs from a trade show handout.
Scannable Over Comprehensive
Reps need information in 3 seconds, not 30 — bold headers, short bullets, visual hierarchy. If a rep can't find the answer mid-call, the doc has failed.
Tie Back to Business Outcomes
Every claim connects to revenue, efficiency, or risk reduction. Replace "AI-powered analytics" with "cut reporting time by 80%."
Sales Deck / Pitch Deck
10-12 Slide Framework
- Current World Problem — The pain your buyer lives with today
- Cost of the Problem — What inaction costs (time, money, risk)
- The Shift Happening — Market or technology change creating urgency
- Your Approach — How you solve it differently
- Product Walkthrough — 3-4 key workflows, not a feature tour
- Proof Points — Metrics, logos, analyst recognition
- Case Study — One customer story told well
- Implementation / Timeline — How they get from here to live
- ROI / Value — Expected return and payback period
- Pricing Overview — Transparent, tiered if applicable
- Next Steps / CTA — Clear action with timeline
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 320 lines · 87 tokens per session scan A 1fb762272e5a
sales-enablement is a skill published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 12d ago), licensed MIT. It adds 87 tokens to every session and 3,074 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to sales-enablement, differing in 102 lines, and is treated as a copy.
Other skills, from other repositories
ad-campaign-analyzer
Analyze cross-channel campaign data, quantify uncertainty, and propose evidence-labeled budget tests without overstating causality.
google-analytics
Skill "google-analytics" from VKirill/claude-lane-stack, covering version requirements (may 2026), usage, use this skill when, do not use this skill when and purpose.
google-tag-manager
Skill "google-tag-manager" from VKirill/claude-lane-stack, covering 🎯 version requirements (june 2026), usage, use this skill when, do not use this skill when and purpose.
agent-injection-boundary-test
Test an authorized AI agent's handling of instructions embedded in retrieved documents or tool outputs using harmless canaries.
ai-citation-verification
Check whether an AI answer's citations actually support its factual claims, with source-location evidence and explicit uncertainty.
ai-evaluation-dataset
Build a versioned JSONL evaluation dataset for an AI workflow, with acceptance criteria, held-out cases, and leakage checks.