Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jbalbu01/sales-enablement-pluginnpx agentmods add commands/jbalbu01/sales-enablement-plugin/content-auditWrote 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/commands/jbalbu01/sales-enablement-plugin/content-audit)<a href="https://agentmods.dev/commands/jbalbu01/sales-enablement-plugin/content-audit"><img src="https://agentmods.dev/badge/commands/jbalbu01/sales-enablement-plugin/content-audit/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/commands/jbalbu01/sales-enablement-plugin/content-audit"><img src="https://agentmods.dev/badge/commands/jbalbu01/sales-enablement-plugin/content-audit.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.00026 | $0.01588 |
| Opus 5.5 | $0.00010 | $0.00635 |
| Sonnet 5.5 | $0.00005 | $0.00318 |
| Haiku 4.5 | $0.00003 | $0.00159 |
Grade A, and why
content-audit 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 1mo 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/content-audit
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Audit your sales enablement content library for freshness, completeness, and alignment. The self-healing system identifies what's stale, what's missing, and what needs immediate attention.
Usage
/content-audit
/content-audit battle cards
/content-audit full audit
Then describe your content library or let me scan what's available.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ CONTENT AUDIT │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Catalog all enablement content with metadata │
│ ✓ Score freshness based on age, events, and outcomes │
│ ✓ Identify content gaps (things reps need but don't have) │
│ ✓ Check content alignment with current messaging/positioning │
│ ✓ Build prioritized remediation plan │
│ ✓ Estimate effort and assign recommended owners │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Knowledge base: Scan content library for all assets │
│ + CRM: Check which content gets used in deals │
│ + Chat: Find requests for content that doesn't exist │
│ + Web: Verify competitive claims are still accurate │
├─────────────────────────────────────────────────────────────────┤
│ SELF-HEALING (automated maintenance) │
│ → Reads memory/content-registry.md for tracked assets │
│ → Applies freshness decay scoring (time + event + outcome) │
│ → Propagates updates through dependency graphs │
│ → Generates refresh tasks automatically │
│ → Logs all changes to memory/changelog.md │
└─────────────────────────────────────────────────────────────────┘
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.
- 1mo ago First seen · 190 lines · 26 tokens per session scan A c7d3195bef10
content-audit is a command published in the GitHub repository jbalbu01/sales-enablement-plugin (17 stars, last pushed 8mo ago), licensed MIT. It adds 26 tokens to every session and 1,588 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
churn-prevention
Win/loss interview + churn analysis + retention playbook. Focuses on retention (not acquisition) — where 80% of the current plugin is focused. For B2B SaaS with churn > 5%/month, consulting with renewal rate < 70%, or a recurring business on a plateau.
audit
Offer diagnostic via the Value Equation — scores 1-10 on each vector (Dream Outcome, Probability, Time Delay, Effort), pinpoints the critical bottleneck, proposes the top 3 concrete levers, and rewrites the offer in 1 paragraph. Recommended prerequisite before LP and script.
client-onboarding
The client's first 30 days after the sale. A structured touch cadence, early quick wins to validate the purchase decision, visible value milestones. Cuts early churn (< 30 days) by a typical 40-60%. For consulting, agencies, cohort programs, mid-market B2B SaaS.
content-hub
30-90 day organic content roadmap. Topic × format × funnel stage × CTA. Healthy mix (60% educational, 25% entertainment, 15% promotional). For the founder/consultant who wants organic compounding over 6-18 months, not one viral post.
Email sequence (cold, warm, nurture, re-engagement). Generates 5-7 sequential emails with hook + agitation + proof + CTA, timing between touches, and context per touch. Tuned for B2B cold outreach — direct voice, no superlatives, specific proof.
help
Interactive decision matrix. Answer 3 questions and get the right command recommended. Useful for onboarding a new client or when you don't know where to start a session. Covers all 17 plugin commands.