Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add uppifyagency/bettercallclaudegrowth/plugin install 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-buddy)<a href="https://agentmods.dev/commands/uppifyagency/bettercallclaudegrowth/gtm-buddy"><img src="https://agentmods.dev/badge/commands/uppifyagency/bettercallclaudegrowth/gtm-buddy/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-buddy"><img src="https://agentmods.dev/badge/commands/uppifyagency/bettercallclaudegrowth/gtm-buddy.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.00073 | $0.00675 |
| Opus 5 | $0.00036 | $0.00338 |
| Sonnet 5 | $0.00015 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
gtm-buddy 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 10d 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gtm-buddy — where do I start?
The plugin's entry point when you don't know which command to use. Describe your situation and get a tailored path: a single skill or the right sequence.
User input: $ARGUMENTS
What to do
-
Classify and route. Launch the gtm-buddy agent, passing it
$ARGUMENTSand the entireuserConfig. The agent readsplaybooks/_index.md+ the archetype playbook, classifies archetype × stage (asking at most 1 disambiguation question if needed), and returns the recommendation in the format: Situation · What you do now (single skill or ordered sequence) · Why · Primary channel + emphasis/what to skip · First action. -
Present the recommendation to the user as-is, and close with the choice:
- "I'll run the sequence automatically", or
- "Run a single step", or
- "Full orchestrated pipeline" (
/gtm).
-
Execution — handled by the main thread, not the
gtm-buddyagent (which is a read-only router and does not write deliverables). Three paths:- Full auto-execution / "do everything for me" → delegate to
/gtm $ARGUMENTS. Thegtm-orchestratoragent (which has Write and Bash) runs the phases with cumulative context, thegtm-criticcheckpoints, the GTM Readiness Score computed with the deterministic scripts, and writesgtm-plan.md. This is the recommended path for end-to-end automatic execution. - Tailored sub-sequence (not the full pipeline, e.g. only
gtm-jobs → gtm-offer → gtm-copy) → the main thread launches the recommended individual/gtm-*commands in order, carrying the context forward step by step and invokinggtm-criticat the playbook checkpoints. For the score of a sub-sequence usenode "${CLAUDE_PLUGIN_ROOT}/scripts/gtm-readiness-score.js" …. - A single step → confirm the single command (e.g.
/gtm-offer …) and stop.
- Full auto-execution / "do everything for me" → delegate to
Principle
gtm-buddy does not replace the specialist commands or the orchestrator: it coordinates them. For zero-state or messy situations it is the most reliable way to avoid taking the wrong path. Never impose the 7-phase pipeline on someone in micro-launch: give the shortest path that works.
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.
- 10d ago First seen · 28 lines · 0 tokens per session scan A a7aa22905e22
gtm-buddy is a command published in the GitHub repository uppifyagency/bettercallclaudegrowth (5 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 675 once invoked, about $0.0004 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.
audit-project-github
This file contains GitHub integration for /audit-project.
design
A command that turns an existing plan into a detailed technical design for building the feature.