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 jbalbu01/sales-enablement-plugin --skill content-healthgit clone --depth 1 https://github.com/jbalbu01/sales-enablement-pluginWrote 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/jbalbu01/sales-enablement-plugin/content-health)<a href="https://agentmods.dev/skills/jbalbu01/sales-enablement-plugin/content-health"><img src="https://agentmods.dev/badge/skills/jbalbu01/sales-enablement-plugin/content-health/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/jbalbu01/sales-enablement-plugin/content-health"><img src="https://agentmods.dev/badge/skills/jbalbu01/sales-enablement-plugin/content-health.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.00147 | $0.03189 |
| Opus 5 | $0.00073 | $0.01595 |
| Sonnet 5 | $0.00029 | $0.00638 |
| Haiku 4.5 | $0.00015 | $0.00319 |
Grade A, and why
content-health 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.
How it starts
The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Health Monitor
The "self-healing" layer of the enablement system. Traditional enablement creates content once and hopes someone remembers to update it. This system actively monitors every asset, detects decay signals, and either auto-refreshes or flags content for human review.
The Decay Problem
Enablement content has a half-life:
- Battle cards decay when competitors ship new features or change pricing (~30 days)
- Playbooks decay when win rates change or process evolves (~90 days)
- Proposals decay when product or pricing changes (~immediate)
- Discovery guides decay when ICP shifts or new personas emerge (~60 days)
- ROI models decay when benchmarks or pricing change (~90 days)
- Buyer personas decay when market conditions shift (~120 days)
If your battle card is 6 months old but your competitor shipped 3 features since then, the rep using that card is fighting with outdated intel.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ CONTENT HEALTH │
├─────────────────────────────────────────────────────────────────┤
│ MONITORING LAYERS │
│ │
│ Layer 1: TIME-BASED │
│ • Track age of every asset in content-registry.md │
│ • Flag when assets exceed their freshness threshold │
│ • Escalate overdue assets in weekly health reports │
│ │
│ Layer 2: EVENT-DRIVEN │
│ • Product change → Flag all assets referencing old info │
│ • Competitor news → Flag related battle cards │
│ • Lost deal → Check if loss reason indicates stale content │
│ • Win rate drop → Investigate if playbook needs refresh │
│ │
│ Layer 3: OUTCOME-BASED │
│ • Track which content gets used and which doesn't │
│ • Identify assets with declining effectiveness │
│ • Surface "zombie content" that exists but nobody uses │
│ │
│ RESPONSE │
│ • Auto-refresh: Update with new data (competitive intel, etc.) │
│ • Flag for review: Alert human when judgment needed │
│ • Propagate changes: When one thing changes, update downstream │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Win rate trends that signal playbook decay │
│ + ~~CRM: Lost deal reasons that expose content gaps │
│ + ~~CRM: Deal stage conversion drops flagging stale process │
│ + ~~competitive intel (ZoomInfo): Competitor tech stack changes │
│ + ~~competitive intel (ZoomInfo): New competitor product launches│
│ + ~~competitive intel (Clay): Company signal changes │
│ + ~~competitive intel (LinkedIn): Competitor hiring & news │
│ + ~~conversation intelligence (Gong): Objection frequency shifts│
│ + ~~conversation intelligence (Gong): Talk track effectiveness │
│ + ~~chat: Rep feedback on stale or missing content │
└─────────────────────────────────────────────────────────────────┘
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 · 301 lines · 147 tokens per session scan A a8b2960bfe46
content-health is a skill published in the GitHub repository jbalbu01/sales-enablement-plugin (14 stars, last pushed 6mo ago), licensed MIT. It adds 147 tokens to every session and 3,189 once invoked, about $0.0007 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 skills, from other repositories
gt-email-infra
Email Infrastructure & Deliverability by Growth Today (growthtoday.co). Expert cold-email infrastructure and deliverability strategist. Use for infrastructure sizing, domain research and purchasing, DNS and auth (MX/SPF/DKIM/DMARC), masking versus redirect, mailbox provisioning, Instantly inbox setup and warmup, going…
gt-linkedin-content
A specialist for organic LinkedIn content aimed at B2B founders and GTM teams. Reach for it on anything across the LinkedIn writing workflow, opening lines and hooks, post structure and storytelling, format choice, posting cadence and timing, comments and engagement, CTAs and comment-gates, profile optimization…
gt-linkedin-outbound
Expert LinkedIn outbound strategist for B2B campaigns by Growth Today (growthtoday.co). Use for LinkedIn cold outreach, DM writing, connection requests, message sequences, personalization, copywriting frameworks, rented engine setup (multi-account infrastructure, daily limits, restrictions, anti-detect browsers…
email-infra-bounce-audit
Audit a bounce or blacklist problem to root cause and produce a full bounce report. Use for pulling replies via the EmailBison MCP/API, working around the broken type=bounced filter, stripping auto-replies, classifying bounces (Hard/Soft/Block) by SMTP/DSN code, running the neutral-copy test, and tracing the cause to…
gt-gtm-strategy-advisor
GTM Strategy Advisor by Growth Today (growthtoday.co) — turns your own CRM data, sales deck, website, and call recordings into a signal-based GTM playbook. Use when a VP of Sales, Head of Growth, RevOps lead, CRO, or founder wants to build, audit, or sharpen their go-to-market motion: define a data-backed ICP, map the…
gt-data-audit
Expert B2B contact data audit framework for RevOps, GTM Engineering, and Sales Operations. Use when running a data quality audit on a CRM (HubSpot, Salesforce, Pipedrive, Close, Attio), scoring a contact data layer across 10 dimensions (coverage, accuracy, freshness, cost, governance, and more), answering benchmark…