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 Avyayalaya/agent-prime --skill pricing-packaginggit clone --depth 1 https://github.com/Avyayalaya/agent-primeWrote 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/avyayalaya/agent-prime/pricing-packaging)<a href="https://agentmods.dev/skills/avyayalaya/agent-prime/pricing-packaging"><img src="https://agentmods.dev/badge/skills/avyayalaya/agent-prime/pricing-packaging.svg" alt="Measured on agentmods" 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.00054 | $0.18586 |
| Opus 5 | $0.00027 | $0.09293 |
| Sonnet 5 | $0.00011 | $0.03717 |
| Haiku 4.5 | $0.00005 | $0.01859 |
Grade A, and why
pricing-packaging 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pricing-packaging — 91% identical, 75 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Produce an elite-tier pricing and packaging strategy document that selects the right monetization model, quantifies willingness-to-pay with evidence-graded confidence, maps competitive pricing positions, architects package tiers with conversion-optimized feature allocation, stress-tests revenue sensitivity, and models the impact of pricing changes on existing customers. The output is a Pricing Strategy Document — not a price list, but a structural assessment of what to charge, why, and what breaks if you are wrong.
When to Use / When NOT to Use
Use this skill when:
- Launching a new product and setting initial pricing
- Redesigning packaging tiers or feature allocation across plans
- Evaluating a price increase or decrease on existing customers
- Responding to a competitor's pricing move
- Designing usage-based or hybrid pricing for AI/SaaS products
- Assessing freemium conversion strategy and free-tier boundaries
- Preparing a pricing recommendation for leadership review
Do NOT use this skill when:
- You need a competitive landscape analysis (use Competitive Market Analysis skill — this skill includes competitive pricing but as one input, not the sole output)
- You need a full go-to-market strategy (pricing is one dimension; GTM includes channels, messaging, launch sequencing)
- You need financial modeling or P&L projections (this skill produces pricing recommendations with revenue sensitivity, not a financial model)
- You need customer research methodology (use Discovery & Research skill — then feed WTP findings into this skill)
Anti-inputs (what this skill does NOT handle):
- Detailed financial modeling or unit economics spreadsheets (this skill produces the pricing strategy that feeds financial models)
- Sales compensation design (adjacent to pricing but separate discipline)
- Contract negotiation tactics (this skill sets the pricing floor and ceiling; negotiation is execution)
- Transfer pricing or internal cost allocation (finance domain, not product pricing)
What ships with it
1 file 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.
- 8d ago First seen · 1,208 lines · 54 tokens per session scan A 2305eadab4da
pricing-packaging is a skill published in the GitHub repository Avyayalaya/agent-prime (8 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 18,586 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 skills, from other repositories
pricing-packaging
Use when designing pricing strategy, packaging tiers, monetization models, or evaluating pricing changes — pricing model selection, willingness-to-pay analysis, competitive pricing maps, package architecture, freemium conversion, usage-based pricing design, or price change impact assessment.
strategy-generate
Create, modify, and optimize quantitative trading strategies, then backtest and evaluate them.
bottleneck-hunter
Supply-chain bottleneck arbitrage. Given a super-trend (AI infra, energy transition, defense, semiconductor reshoring, space economy), decompose its physical supply chain down to Layer 2/3 choke points (optics, lasers, InP/SOI substrates, IC substrates, probe cards, specialty fiberglass...) and surface under-the-radar…
execution-model
Trade execution modeling (backtest only) — slippage formulas (linear / square-root impact), VWAP/TWAP execution logic, market-impact cost estimation, and execution-assumption configuration.
ml-strategy
Machine-learning predictive strategy based on sklearn walk-forward training, feature engineering, and signal generation. Suitable for any OHLCV data.
event-driven
Event-driven strategy based on sentiment-scored signals from news, announcements, and macro events. The LLM acts as the NLP engine, and event data follows a CSV schema.