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 beingsmit/technical-product-gtm --skill technical-product-pricinggit clone --depth 1 https://github.com/beingsmit/technical-product-gtmWrote 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/beingsmit/technical-product-gtm/technical-product-pricing)<a href="https://agentmods.dev/skills/beingsmit/technical-product-gtm/technical-product-pricing"><img src="https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/technical-product-pricing/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/beingsmit/technical-product-gtm/technical-product-pricing"><img src="https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/technical-product-pricing.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.00046 | $0.02943 |
| Opus 5 | $0.00023 | $0.01471 |
| Sonnet 5 | $0.00009 | $0.00589 |
| Haiku 4.5 | $0.00005 | $0.00294 |
Grade A, and why
technical-product-pricing 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 11d 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.
This is a copy
98% identical to gtm-technical-product-pricing — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Product Pricing
Initial Assessment
Before recommending pricing, understand:
- Product type: API/platform, developer tool, SaaS application, infrastructure?
- Current pricing: What do you charge now? How long has it been this way?
- GTM motion: Self-serve, sales-assisted, enterprise, or hybrid?
- Cost structure: What's your marginal cost per customer/user/unit?
- Competitive landscape: What do alternatives cost? (Including "do nothing")
Core Frameworks
1. The Price Increase Nobody Noticed (You're Probably Underpriced)
The Pattern:
Platform company, growth stage. Pricing hadn't changed since launch. Enterprise customers paying $15K/year for a product saving them $200K+ in engineering time.
Leadership debate: "If we raise prices, we'll lose customers."
What actually happened:
Raised enterprise tier from $15K to $45K/year. Added dedicated support, SSO, audit logs to justify the jump.
Lost: 0 enterprise customers. Zero.
Gained: 3x revenue per enterprise account. Plus the customers who stayed started taking the product more seriously — higher adoption, more internal champions, more expansion.
Why This Happens:
Technical founders anchor pricing to cost ("it costs us $X to serve them, so we charge $2X"). Enterprise buyers anchor pricing to value ("this saves us $200K, so $45K is cheap").
The Pricing Sanity Check:
For every customer segment, calculate:
Value Ratio = Customer's alternative cost / Your price
If Value Ratio > 10x → You're massively underpriced
If Value Ratio > 5x → You're underpriced (most startups are here)
If Value Ratio 3-5x → Healthy pricing
If Value Ratio < 3x → Approaching ceiling
If Value Ratio < 2x → You're expensive (need strong differentiation)
How to Calculate Alternative Cost:
- Hours spent on manual process × hourly rate × frequency
- Cost of building in-house (engineers × months × loaded cost)
- Cost of existing tool + switching cost + productivity loss during transition
- Cost of not solving the problem (incidents, downtime, churn)
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.
- 11d ago First seen · 355 lines · 46 tokens per session scan A 27b6d4ab3a6c
technical-product-pricing is a skill published in the GitHub repository beingsmit/technical-product-gtm (42 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 2,943 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to gtm-technical-product-pricing, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
seo-strategy
Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
youtube-producer
Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…
support-operations
Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. Use this to set up or fix support operations, choose channels, size a team, set or renegotiate service levels, reduce cost per contact, diagnose long queues or poor…