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-jobs)<a href="https://agentmods.dev/commands/uppifyagency/bettercallclaudegrowth/gtm-jobs"><img src="https://agentmods.dev/badge/commands/uppifyagency/bettercallclaudegrowth/gtm-jobs/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-jobs"><img src="https://agentmods.dev/badge/commands/uppifyagency/bettercallclaudegrowth/gtm-jobs.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.00043 | $0.00931 |
| Opus 5 | $0.00022 | $0.00465 |
| Sonnet 5 | $0.00009 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
gtm-jobs 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gtm-jobs - Jobs to Be Done in Christensen style
This command applies the christensen-jobs skill (Jobs Theory from Competing Against Luck). It is the upstream demand-side layer: it defines what progress the customer is seeking, not what you sell. Its outputs constrain positioning, offer, and copy. Respect userConfig.output_language (IT by default), userConfig.industry, userConfig.brand_voice, and userConfig.default_channel.
User input: $ARGUMENTS
Steps
-
Load the skill. Invoke the
christensen-jobsskill by name (it activates from its description; do not use file paths) and apply its frameworks, going deeper with cheatsheets/patterns when needed. Do NOT copy the book's content: use it only as an operating lens. -
Define the Job(s). For $ARGUMENTS write the job as a sentence — "When [circumstance], help me [progress, verb], so I can [deeper purpose]" — using verbs and nouns, never adjectives. Check the level of abstraction (broad enough to see the true competitive set, narrow enough to guide design). If the circumstances differ, isolate distinct jobs (the "Milk Shake Dilemma"): same product, different jobs → different messages and tiers.
-
Map the three dimensions. For each job make the functional, social, and emotional components explicit. Flag where the social/emotional is underweighted: that is usually where you win and where generic competitors (Google, AI, commodities) cannot follow.
-
Pinpoint the circumstance and the struggling moment. Define the trigger (precipitating event) and the time window. This is what targeting and forms must read — not demographics.
-
Frame the real competitive field. Always include nonconsumption ("competing with nothing" / the DIY route) and workarounds/compensating behaviors. What does the customer "fire" to "hire" your solution?
-
Analyze the Forces of Progress. Map the four forces: Push of the situation + Pull of the solution (which drive change) vs Habit of the present + Anxiety (of choosing + of using) which hold it back. The switch happens only if push+pull > habit+anxiety. Indicate the binding constraint and the cheapest lever (often reducing anxiety/habit, not adding features).
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 · 35 lines · 43 tokens per session scan A 7cd1d6d63108
gtm-jobs is a command published in the GitHub repository uppifyagency/bettercallclaudegrowth (5 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 931 once invoked, about $0.0002 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.