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.
git clone --depth 1 https://github.com/uppifyagency/bettercallclaudegrowthWrote 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/uppifyagency/bettercallclaudegrowth/gtm)<a href="https://agentmods.dev/commands/uppifyagency/bettercallclaudegrowth/gtm"><img src="https://agentmods.dev/badge/commands/uppifyagency/bettercallclaudegrowth/gtm/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/uppifyagency/bettercallclaudegrowth/gtm"><img src="https://agentmods.dev/badge/commands/uppifyagency/bettercallclaudegrowth/gtm.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.00064 | $0.00830 |
| Opus 5 | $0.00032 | $0.00415 |
| Sonnet 5 | $0.00013 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
gtm 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gtm - Adaptive Go-To-Market pipeline
This command does NOT apply a single skill: it starts the end-to-end GTM pipeline by delegating to the gtm-orchestrator agent. Always respect userConfig (output_language IT default, archetype, stage, industry, brand_voice, default_channel).
Not sure whether you need the full pipeline or a single step? Use
/gtm-buddy <situation>: it classifies your case and routes you (single skill or sequence), then can launch this pipeline for you.
What to do
- Launch the gtm-orchestrator agent, passing it
$ARGUMENTS(product, target, goal) and the entireuserConfig. - The orchestrator runs Phase 0 (classifies archetype × stage by reading
playbooks/_index.md+ the relevant playbook) and calibrates the phases accordingly: short path formicro-launch, full forscaling, with an initial audit forestablished. - It runs the active phases in sequence, calling by name the relevant skill(s) (auto-activation), maintaining the cumulative context.
- At the CHECKPOINTs it invokes the gtm-critic agent for the red-team and integrates the findings.
- It applies the PERCEIVE → ANALYZE → VALIDATE → ACT synthesis with falsifiability conditions and computes the GTM Readiness Score (0-100).
- It consolidates everything into the final deliverable
gtm-plan.md.
The 7 phases (default; the playbook modulates them by archetype/stage)
- JOBS, POSITIONING & ICP ->
christensen-jobs(demand-side) →butcher-productize+doing-content-right - OFFER ->
hormozi-offers· CHECKPOINT gtm-critic: offer red-team - LEAD GENERATION ->
hormozi-leads(Core Four prioritized according to the playbook) - CONTENT & COPY ->
doing-content-right+drew-sucks-framework - CHANNELS ->
seo-2026-sota|instagram-performance-marketing— primary channel from the archetype's playbook; ifuserConfig.default_channel≠auto, respect it; the other channels in summary - EMAIL & NURTURING ->
advanced-email-marketing - MEASUREMENT & ITERATION -> the playbook's north-star KPI + loop · CHECKPOINT gtm-critic: funnel red-team (+ SUCKS copy audit from phase 4)
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 · 36 lines · 64 tokens per session scan A e5fbb2b0062a
gtm is a command published in the GitHub repository uppifyagency/bettercallclaudegrowth (5 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 830 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-31.
Other commands, from other repositories
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
ccc-orchestrate
Sequential and tmux/worktree orchestration guidance for multi-agent workflows.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
design
A command that turns an existing plan into a detailed technical design for building the feature.
audit-project-github
This file contains GitHub integration for /audit-project.