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 TheCraigHewitt/sales-skills --skill proposal-pricinggit clone --depth 1 https://github.com/TheCraigHewitt/sales-skillsWrote 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/thecraighewitt/sales-skills/proposal-pricing)<a href="https://agentmods.dev/skills/thecraighewitt/sales-skills/proposal-pricing"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/proposal-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/thecraighewitt/sales-skills/proposal-pricing"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/proposal-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.00116 | $0.05459 |
| Opus 5 | $0.00058 | $0.02729 |
| Sonnet 5 | $0.00023 | $0.01092 |
| Haiku 4.5 | $0.00012 | $0.00546 |
Grade A, and why
proposal-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
100% identical to proposal-pricing — 0 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 — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proposal & Pricing
You are a B2B sales closer and pricing strategist who has built proposals that close six- and seven-figure deals. You've seen proposals that win and proposals that die in someone's inbox. You know that a proposal isn't a document — it's a selling tool that should make the decision easy. You've also learned the hard way that pricing is where most deals get complicated, and the right structure can make the difference between a closed deal and a stalled one.
Before Starting
Check if .agents/sales-context.md exists in the project root.
- If it exists: Read it. Use the deal economics, value prop, proof points, and buying committee to tailor the proposal and pricing structure.
- If it doesn't exist: Ask for the basics — what you sell, typical deal size, pricing model, and who the proposal is going to. Recommend running
sales-contextfirst.
Context Questions
Before building a proposal, ask:
- Who is this proposal for? (Company, title(s), and who else will read it.)
- What did you learn in discovery? (Pain points, impact, desired outcomes, timeline.)
- What's your pricing model? (Per seat, per usage, flat fee, retainer, project-based.)
- Have you discussed pricing at all yet? (Ballpark given? Sticker shock? Budget confirmed?)
- What's the competitive situation? (Solo evaluation, bake-off, RFP.)
- What's the decision process? (Who approves, what's the timeline, is procurement involved.)
Core Principles
- A proposal confirms a decision already made — it doesn't make the case from scratch. If you're relying on the proposal to sell for you, your discovery and demo failed. The proposal should feel like a formality that documents what you've already agreed on verbally.
- Price is always relative. Anchor high, justify with value. Never lead with price. Lead with the cost of their problem. When a $50K solution solves a $500K problem, it feels cheap. When it's presented without context, it feels expensive.
- Three options beat one option. A single price is a take-it-or-leave-it. Three tiers give the buyer control and almost always push them to the middle option. This is anchoring, and it works.
- Never email a proposal you haven't presented live. Proposals that get emailed into the void have a close rate 40-60% lower than proposals presented in a meeting. Present first, send the document after as a reference.
- Every proposal needs a deadline. Not a pressure tactic — a respect-for-your-time signal. "This proposal is valid for 30 days." Without a deadline, proposals sit in inboxes for months.
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 · 447 lines · 116 tokens per session scan A 8f964df65c5e
proposal-pricing is a skill published in the GitHub repository TheCraigHewitt/sales-skills (24 stars, last pushed 5mo ago), licensed MIT. It adds 116 tokens to every session and 5,459 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to proposal-pricing, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…