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 etrebels/claude-code-growth-os --skill account-healthgit clone --depth 1 https://github.com/etrebels/claude-code-growth-osWrote 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/etrebels/claude-code-growth-os/account-health)<a href="https://agentmods.dev/skills/etrebels/claude-code-growth-os/account-health"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/account-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/etrebels/claude-code-growth-os/account-health"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/account-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.00668 |
| Opus 5 | $0.00030 | $0.00334 |
| Sonnet 5 | $0.00012 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
account-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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Account Health
The right-side operating skill — the equivalent of lead-qualify for the post-sale half of the bowtie. Where lead-qualify scores a deal's fit, this scores a customer's health: is value landing, is the renewal safe, is there room to grow? It reads the account book and writes the signal back into the same loop the field uses.
From ops/customers.md (or a single account the user names) and any recent post-sale notes:
-
Read the adoption signal. Against the account's value hypothesis — is the customer getting what they bought this to do? Usage trend, workflows live vs. in scope, who's actually using it.
-
Score it green / amber / red:
- 🟢 Green — using it as intended, champion engaged, value visible.
- 🟡 Amber — one warning sign (a stalled workflow, a quiet month, a single thread).
- 🔴 Red — value not landing: usage down, champion gone quiet, or single-threaded after a change.
-
Watch the renewal clock. The renewal motion starts at day 60, not day 85. If the renewal date is inside 60 days, say so and start the motion now — don't wait for the contract to surface it.
-
Flag churn early-warnings. Name the leading indicators, not the lagging one: usage trending down, the champion gone quiet, a single-threaded account after a reorg. These precede a lost renewal; the cancellation is just when it becomes visible. When one fires, hand the recovery to
churn-save. -
Spot expansion-readiness. A healthy account using the core well, or a second team asking unprompted, is an expansion signal — not a renewal risk. Work it with
expansion-signal. -
Write the signal to the loop and update the book. Log a tagged line in
ops/feedback-log.md— the same single home marketing and product read:RETENTION-RISK: [account] — [the adoption/churn signal] → [CS or product action]EXPANSION-SIGNAL: [account] — [the readiness signal] → hand to sales with CS context
Then update the account's stage, key signal, and next step in
ops/customers.md.
Don't tag every quiet week as a risk — flag it when usage, the champion, or the value story is actually slipping. A book full of false alarms gets ignored.
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 · 32 lines · 60 tokens per session scan A a51ed9093c5b
account-health is a skill published in the GitHub repository etrebels/claude-code-growth-os (20 stars, last pushed 6d ago), licensed MIT. It adds 60 tokens to every session and 668 once invoked, about $0.0003 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
startup-launch-playbook
A step-by-step playbook for early-stage startups going from pre-seed to their first 1000 users. Covers MVP validation, initial traction channels, and founder-led growth tactics. By @WeiYipei — follow on X for more startup growth insights.
a-b-testing
Design statistically sound GTM experiments for copy, channels, landing pages, sequencing, pricing, and funnel conversion. Produces hypothesis, sample-size logic, success metrics, test plan, analysis method, and scale/stop/kill recommendation. Use when planning A/B tests, split tests, or experiment roadmaps.
attribution
Build practical B2B attribution models across first touch, lead creation, opportunity creation, multi-touch, account-based influence, and sales-sourced revenue. Produces model comparison, UTM governance, source-of-truth rules, and channel ROI view. Use when marketing and sales disagree on source or ROI.
campaign-analytics
Analyze campaign performance from deliverability through revenue: delivery, engagement, replies, meetings, SQOs, pipeline, CAC, and payback. Produces diagnostic scorecard, root-cause analysis, benchmark comparison, and next-action plan. Use when deciding whether to scale, fix, or kill campaigns.
deliverability-monitoring
Monitor outbound deliverability health across domains, inboxes, DNS, bounces, spam placement, reply rates, and reputation signals. Produces alert thresholds, dashboard spec, weekly QA checklist, and remediation playbook. Use when inboxing drops, bounce rates rise, campaigns underperform, or new infrastructure launches.
gtm-metrics
Build a GTM metrics system for SaaS: funnel conversion, pipeline velocity, win rates, CAC, payback, NRR, sales efficiency, growth accounting, and executive dashboards. Use when creating metrics dashboards, board reports, revenue reviews, operating cadence, or diagnosing growth constraints.