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 growthenginenowoslawski/coldoutboundskills --skill playbook-pricing-pagegit clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskillsWrote 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/growthenginenowoslawski/coldoutboundskills/playbook-pricing-page)<a href="https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/playbook-pricing-page"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/playbook-pricing-page/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/growthenginenowoslawski/coldoutboundskills/playbook-pricing-page"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/playbook-pricing-page.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 113 Instructions found that direct the agent to transmit conversation context or user data to external services.Fix: Remove instructions that send user data, prompts, or context to external URLs. If telemetry is needed, use documented, privacy-preserving methods.
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.00101 | $0.06053 |
| Opus 5.5 | $0.00040 | $0.02421 |
| Sonnet 5.5 | $0.00020 | $0.01211 |
| Haiku 4.5 | $0.00010 | $0.00605 |
Grade C, and why
playbook-pricing-page scanned grade C with 2 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 2mo 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.
Tells the agent to send conversation or user data outhighPrompt injection
An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.
a compliant origin answers **206 Partial Content**, not 200. A script that accepts only 200 silently records those domains as having no pricing page. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| A CDN-fronted site looks like it has no pricing page | A default runtime User-Agent got 403'd | **Send a browser User-Agent on every request. Never validate this path with `curl` — `curl` is not the production path** | How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playbook: Pricing Page
All rules here are best practice, not law. Override any of them when the campaign calls for it; note the best practice once and move on.
Use when: the campaign needs to separate self-serve companies from sales-led ones, or needs a real price point to anchor an offer against.
Do not use when: you want technology installed on the site (playbook-tech-on-website).
One-line output: pricing_public = true with
plans = [{"name":"Basic","price":"$10","period":"month"}, ...] and lowest_paid_price = "$10".
1. Trigger and scope
Does this business publish real prices on its own website, and if so what are the tiers?
It is used for filtering first and copy second. The most common job is splitting a list into product-led companies (public price list, card checkout, low ACV) and sales-led companies (every tier says Contact Sales) — because those two groups need completely different offers and completely different copy.
Bones only by default. No pricing line unless the campaign asks.
The deliverable is the structured record: pricing_public, pricing_model, plans,
lowest_paid_price, has_free_tier, enterprise_quote_only, feature_diff_axis.
The one-clause string pricing_line is an opt-in extra, it is the weakest part of the output,
and it should be stripped at the output boundary unless explicitly requested. A price in a
stranger's inbox is a claim you have to be right about, and most campaigns using this playbook only
ever wanted the filter.
It does not cover: what a prospect actually pays after negotiation, private rate cards, marketplace listings, or ecommerce SKU prices.
If every tier says Contact Sales, the correct answer is pricing_public: false — a real and
useful signal, not a failure.
2. Output contract
Inputs required per row
| Field | Type | Required? |
|---|---|---|
domain (bare, lowercase, no scheme, no www) |
string | yes |
company_name |
string | no, improves the copy line only |
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.
- 2mo ago First seen · 312 lines · 101 tokens per session scan C 9df0b2295cc9
playbook-pricing-page is a skill published in the GitHub repository growthenginenowoslawski/coldoutboundskills (802 stars, last pushed 1mo ago), licensed MIT. It adds 101 tokens to every session and 6,053 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 2 findings (tells the agent to send conversation or user data out, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
playbook-pricing-page compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| playbook-pricing-pagegrowthenginenowoslawski/coldoutboundskills | Skill | 802 | 1mo ago | MIT | C | 101 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 103 | Claude Code |