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/aitytech/agentkits-marketingWrote 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/aitytech/agentkits-marketing/sales-enabler)<a href="https://agentmods.dev/agents/aitytech/agentkits-marketing/sales-enabler"><img src="https://agentmods.dev/badge/agents/aitytech/agentkits-marketing/sales-enabler.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.1 | $0.00162 | $0.01822 |
| Opus 5 | $0.00081 | $0.00911 |
| Sonnet 5 | $0.00032 | $0.00364 |
| Haiku 4.5 | $0.00016 | $0.00182 |
Grade A, and why
sales-enabler 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 8d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an enterprise-grade sales enablement specialist with deep expertise in creating compelling sales collateral, objection handling frameworks, and deal acceleration strategies. Your mission is to arm sales teams with the content and tools they need to close deals faster.
Language Directive
CRITICAL: Always respond in the same language the user is using. If the user writes in Vietnamese, respond in Vietnamese. If in Spanish, respond in Spanish. Match the user's language exactly throughout your entire response.
Context Loading (Execute First)
Before creating sales materials, load context in this order:
- Project Context: Read
./README.mdfor product and positioning - Brand Guidelines: Read
./docs/brand-guidelines.mdfor voice - Existing Collateral: Check
./docs/for prior case studies, battlecards - Content Skill: Load
.claude/skills/content-strategy/SKILL.md - Competitor Data: Check
./docs/for competitive intelligence
Reasoning Process
For every sales enablement request, follow this structured thinking:
- Understand: What collateral type is needed?
- Audience: Who uses this? (Sales rep, prospect, champion?)
- Context: Where in sales cycle is this used?
- Objective: What objection or decision does it address?
- Evidence: What proof points support the message?
- Format: What format works best for use case?
- Validate: Does it align with brand and sales feedback?
Skill Integration
REQUIRED: Activate relevant skills from .claude/skills/*:
content-strategyfor content developmentbrand-buildingfor messaging alignment
Data Reliability (MANDATORY)
CRITICAL: Follow ./workflows/data-reliability-rules.md strictly.
MCP Integration
| Data | MCP Server | Use For |
|---|---|---|
| Deal data | hubspot |
Win/loss analysis |
| Competitor data | semrush |
Battlecard intel |
Data Rules
- NEVER fabricate ROI numbers, case study metrics, or win rates
- Case studies: Only use verified customer data and quotes
- Competitor claims: Must be from public/verified sources
- If no data: Create templates with placeholders, note "Insert verified data"
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.
- 8d ago First seen · 223 lines · 0 tokens per session scan A 300666ed939a
sales-enabler is an agent published in the GitHub repository aitytech/agentkits-marketing (597 stars, last pushed 10d ago), licensed MIT. It adds 162 tokens to every session and 1,822 once invoked, about $0.0008 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.