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 shalintripathi/saas-marketing-agents --skill growth-opsgit clone --depth 1 https://github.com/shalintripathi/saas-marketing-agentsWrote 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/shalintripathi/saas-marketing-agents/growth-ops)<a href="https://agentmods.dev/skills/shalintripathi/saas-marketing-agents/growth-ops"><img src="https://agentmods.dev/badge/skills/shalintripathi/saas-marketing-agents/growth-ops/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/shalintripathi/saas-marketing-agents/growth-ops"><img src="https://agentmods.dev/badge/skills/shalintripathi/saas-marketing-agents/growth-ops.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.00378 | $0.01889 |
| Opus 5.5 | $0.00151 | $0.00756 |
| Sonnet 5.5 | $0.00076 | $0.00378 |
| Haiku 4.5 | $0.00038 | $0.00189 |
Grade A, and why
growth-ops 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 23d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth Operations
Step 0 (always first): Load brand context
Before producing any deliverable, look for a brand-context.md file in the user's project root (also check ./.claude/brand-context.md and ./docs/brand-context.md). It holds the company's ICP, positioning, messaging pillars, citable proof, voice, banned words, and compliance constraints.
- If it exists: read it in full and treat it as binding for this run. Hand its contents to every specialist agent you route work to, alongside the task brief. Its "Rules for agents reading this file" section overrides an agent's own defaults.
- If it does not exist: say so, point the user at the template (
templates/brand-context.md), and offer to generate a filled draft by interviewing them or by reading their website and existing content. Then proceed with explicitly-labelled assumptions — never silently invented ones.
Non-negotiable regardless of which path applies: do not invent customer names, metrics, funding, integrations, certifications, or outcomes. Only proof recorded in brand-context.md (or supplied directly in the request) may be used as fact. Where a claim would help but no evidence exists, emit a [NEEDS INPUT: …] marker in the deliverable rather than a plausible-sounding guess.
What This Is
Growth Operations owns the two revenue surfaces that sit outside the classic top-of-funnel: the self-serve funnel inside the product (signup → activation → first paid invoice) and the installed base (adoption, expansion, churn-save, renewal). Most marketing teams staff neither and wonder why acquisition spend keeps rising while net revenue retention slips. This skill routes self-serve and lifecycle-of-the-customer questions to the specialist who owns them, and hands anything pre-signup back to the acquisition skills.
The Team: 3 Specialist Agents
| # | Agent | File | What They Do |
|---|---|---|---|
| 1 | PLG Activation Strategist | agents/growth-plg-activation-strategist.md |
Owns the self-serve funnel from signup to first paid invoice: activation-event and time-to-value definition, free-trial vs freemium vs reverse-trial decisions, in-product onboarding briefs, PQL definition and signal spec, upgrade moments and paywall placement, and the PQL-to-sales-assist handoff. |
| 2 | Interactive Demo Strategist | agents/growth-interactive-demo-strategist.md |
Owns the self-guided interactive demo — the product experience in front of the login wall: the demo portfolio and the job each demo does, flow scripts and checkpoints, gate policy read as a measurement decision, build modality and its freshness debt, a register giving every published demo an owner, a release-bound re-capture trigger and an expiry, purpose-built seed data with no live-account capture, step-level instrumentation with stated denominators, and the controlled comparison required before a demo uplift is called a cause. |
| 3 | Customer Marketing Lead | agents/growth-customer-marketing-lead.md |
Owns net revenue retention as a marketing target: feature-adoption campaigns, expansion and cross-sell plays to the installed base, churn-save and win-back programs, the self-serve cancel flow (reason-matched save offers measured by survival against a no-offer holdout) and failed-payment dunning recovery by decline type, renewal marketing, customer-base segmentation by health and expansion potential, and the champion move: a watchlist of the people who actually bought and used the product at each paying account, a job change confirmed from the experience record rather than a headline, and the two plays one move fires (re-onboard the seat they left; route the account they joined, with the sender decided by outbound or ABM). |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 23d ago Changed · +73 tokens per session a332175fadca
- 1mo ago Changed · +42 tokens per session 42eae3550486
- 1mo ago Changed · +8 lines · +123 tokens per session 087871ef1f88
- 2mo ago First seen · 61 lines · 140 tokens per session scan A 0430ae6450dc
growth-ops is a skill published in the GitHub repository shalintripathi/saas-marketing-agents (30 stars, last pushed yesterday), licensed MIT. It adds 378 tokens to every session and 1,889 once invoked, about $0.0015 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-31.
Other skills, from other repositories
batch-process
Batch-produce many content pieces as one resumable queue, highest priority first. "write these 15 posts".
cf-aeo-check
Re-check a published piece's AEO: cited in AI Overviews and AI answers, tracked over time. "did AI cite our article".
image-seo-audit
Audit image SEO on a page: alt text, weight, formats, srcset, lazy loading, CLS. "audit our image SEO".
content-brief
Write an executable content brief: keyword map, outline, intent, SEO checklist. "write a brief for this topic".
email-sequence
Design an ESP-ready email sequence: subjects, copy, timing, branching, deliverability. "build a welcome sequence".
build-review-gallery
Build the shareable HTML review gallery of every generated post for team or client. "make me a gallery page".