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 swan-gtm/gtm-skills --skill weekly-expansion-scangit clone --depth 1 https://github.com/swan-gtm/gtm-skillsWrote 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/swan-gtm/gtm-skills/weekly-expansion-scan)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/weekly-expansion-scan"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/weekly-expansion-scan/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/swan-gtm/gtm-skills/weekly-expansion-scan"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/weekly-expansion-scan.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.00152 | $0.02211 |
| Opus 5.5 | $0.00061 | $0.00884 |
| Sonnet 5.5 | $0.00030 | $0.00442 |
| Haiku 4.5 | $0.00015 | $0.00221 |
Grade A, and why
weekly-expansion-scan 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 9d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Applies when the question is "of everyone already paying us, who is ready to grow, and who do we call first?" Produces a ranked weekly digest, one entry per account, each with a named contact and a specific suggested move.
Expansion revenue is usually lost to neglect, not to competitors. The customers most ready to upgrade are often the quiet ones: a mid-size company on your cheapest plan, or a team that has burned 90% of its allowance three weeks before renewal. A weekly scan with fixed scoring rules catches them before the customer has to ask, or leaves.
Template placeholders
Replace every {{...}} before enabling. See the setup checklist reference for the full list and the decisions behind each.
{{BILLING_SOURCE}}: Where active subscriptions live (e.g. Stripe, Chargebee, your product database){{CRM}}: Your CRM (e.g. HubSpot, Salesforce, Attio){{CLOSED_WON_STAGE}}: The CRM stage or lifecycle value that marks a paying customer{{TIER_TAGS}}: Your account tiers, top two used here (default: Diamond and Gold; lower tiers are excluded){{ACV_TAGS}}: Your ACV potential tags (default: high, medium, low){{USAGE_UNIT}}: What customers consume on a plan (e.g. credits, seats, API calls, records){{PLAN_LADDER}}: Your plans with price and included{{USAGE_UNIT}}, lowest to highest{{SCALE_PRICE}}: Monthly price of the plan you expect a mature customer to sit on (default thresholds below assume about $1,200 a month){{EXPANSION_TARGETS_FILE}}: Optional: a maintained list of target accounts with their expansion angle and status{{DIGEST_CHANNEL}}: Where the digest posts (e.g. a #expansion-leads Slack channel){{ERROR_CHANNEL}}: Where run failures post{{EXPANSION_OWNER}}: The person who works expansion conversations
Step 1: Build the working universe
- Pull every active subscription with a price above zero from
{{BILLING_SOURCE}}: account domain, plan, monthly price, included{{USAGE_UNIT}}, remaining{{USAGE_UNIT}}this cycle, billing interval. Page through until you have all of them. - Pull every account at
{{CLOSED_WON_STAGE}}from{{CRM}}. - The working universe is the intersection: in the closed-won stage AND paying. Drop any domain that appears in only one source, and log the mismatches; they are usually billing or CRM hygiene problems worth a separate look.
What ships with it
1 file 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.
- 9d ago First seen · 147 lines · 152 tokens per session scan A 6dcc435efdd8
weekly-expansion-scan is a skill published in the GitHub repository swan-gtm/gtm-skills (221 stars, last pushed 8d ago), licensed MIT. It adds 152 tokens to every session and 2,211 once invoked, about $0.0006 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-10-19.
Other skills, from other repositories
Pipedrive Automation
Automate Pipedrive CRM workflows including deal management, pipeline tracking, and sales reporting.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
html-ppt-product-launch
OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.
afrexai-lead-hunter
Enterprise-grade B2B lead generation, enrichment, scoring, and outreach sequencing for AI agents. Find ideal prospects, enrich with verified data, score against your ICP, and generate personalized outreach — all autonomously.
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.
icp-scoring
Score and tier ICP-fit accounts using firmographic, technographic, intent, pain, and timing signals. Produces a weighted ICP scorecard, tiering rules, anti-ICP exclusions, routing thresholds, and validation checklist. Use when defining target accounts, ranking TAM lists, prioritizing ABM accounts, or building fit…