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.
git 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/rules/rajitsaha/100xprism/sales-enablement)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/sales-enablement"><img src="https://agentmods.dev/badge/rules/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/rules/rajitsaha/100xprism/sales-enablement"><img src="https://agentmods.dev/badge/rules/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.00036 | $0.03039 |
| Opus 5 | $0.00018 | $0.01520 |
| Sonnet 5 | $0.00007 | $0.00608 |
| Haiku 4.5 | $0.00004 | $0.00304 |
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 5d 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 — 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 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.
- 5d ago First seen · 320 lines · 3,039 tokens per session scan A 2f177321b0ef
sales-enablement is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 3,039 once invoked, about $0.0002 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.