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 GTMify/aigtm --skill pricing-strategygit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/pricing-strategy)<a href="https://agentmods.dev/skills/gtmify/aigtm/pricing-strategy"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/pricing-strategy/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/gtmify/aigtm/pricing-strategy"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/pricing-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.01663 |
| Opus 5.5 | $0.00031 | $0.00665 |
| Sonnet 5.5 | $0.00016 | $0.00333 |
| Haiku 4.5 | $0.00008 | $0.00166 |
Grade A, and why
pricing-strategy 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 1mo 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Strategy
Your Role
You are a pricing and packaging strategist who treats pricing as a product decision, not a finance afterthought. You design tiers, value metrics, and price points that align with how customers derive value — and you tell the truth about when pricing is the problem versus when it's a symptom of weaker positioning or product fit.
Process
Step 1: Diagnose the Current Pricing
Capture:
- Current pricing model: Tiers, prices, what's included, value metric (per seat, per usage, flat, per event)
- Average deal size and split by tier
- Conversion patterns: Where deals tend to get stuck, what customers ask for, what they push back on
- Customer feedback verbatim: "Too expensive," "missing X," "wish I could pay less for fewer features"
- Competitive pricing: What 3-5 alternatives charge (public pricing only)
- The trigger: Why pricing is being revisited (low conversion, churn, expansion, price compression, repositioning)
If the diagnosis surfaces a positioning or product gap, say so. Pricing changes don't fix product problems.
Step 2: Pick the Value Metric
The value metric is what you charge per. Get this right and tiers become easy. Get it wrong and pricing fights you forever.
| Metric | When it works | When it breaks |
|---|---|---|
| Per seat | Each user gets value individually | Power users + casual users mixed in one org |
| Per usage (events, queries, API calls) | Value scales with consumption | Customers fear unpredictable bills |
| Per workflow / outcome | Value tied to a discrete result | Hard to count, easy to game |
| Per record / asset | Value scales with data volume | Customers buy then sit on data |
| Tiered flat | Value lumpy by company size | Doesn't scale with high-value customers |
| Hybrid | Different stakeholders value different things | Can become confusing if too many dimensions |
Pick one primary value metric. Use a second only if it captures distinct value (e.g., per seat + per usage for collaboration tools).
What ships with it
2 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.
- 1mo ago First seen · 151 lines · 78 tokens per session scan A 1b052b2ded20
pricing-strategy is a skill published in the GitHub repository GTMify/aigtm (25 stars, last pushed 23d ago), licensed MIT. It adds 78 tokens to every session and 1,663 once invoked, about $0.0003 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-30.
Other skills, from other repositories
activity-capture-diagnostic
Diagnose sales activity capture quality across a team and grade it A through F. Computes per-rep capture rate, under-loggers below team median, phantom-progression opportunities (stage advanced with zero logged activity), activity type mix, and the correlation between capture rate and win rate. Use when the user asks…
lead-routing-rule-analyzer
Diagnose lead routing health and grade it A through F. Computes speed-to-lead (creation-to-assignment and assignment-to-first-touch) with percentiles, SLA violations, orphaned leads, distribution imbalance across reps, and routing leakage (assigned rep territory does not match lead territory). Use when the user asks…
salesforce-revops-audit
Run a comprehensive Salesforce RevOps health audit across five dimensions (pipeline health, data quality, forecast hygiene, deal integrity, process integrity) and produce a graded report (A through F) with a prioritized remediation queue. Use as the entry point for any new Salesforce org assessment, before a new…
deal-investigator
Produce a structured deal review for a single opportunity. Pulls activity, stage progression, comparable deals, and risk indicators. Use when a manager needs to pressure-test a specific deal, prepare for a deal review, decide whether to escalate, or determine if a deal is real before the forecast call.
forecast-call-prep
Prepare the executive summary for a weekly forecast call by reconciling rep commits against historical close-rate models and surfacing material variance. Use when the user asks for forecast call prep, weekly forecast review, forecast variance analysis, or a Monday morning forecast memo.
pipeline-hygiene-audit
Audit a sales team's open pipeline for hygiene issues and produce a per-rep punchlist of fixes ranked by severity. Use when the user asks for pipeline hygiene, data quality check, stale opp report, pipeline cleanup, or CRM cleanup before a forecast call or QBR.