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 negotiationgit 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/negotiation)<a href="https://agentmods.dev/skills/thecraighewitt/sales-skills/negotiation"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/negotiation/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/negotiation"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/negotiation.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.00127 | $0.05530 |
| Opus 5 | $0.00063 | $0.02765 |
| Sonnet 5 | $0.00025 | $0.01106 |
| Haiku 4.5 | $0.00013 | $0.00553 |
Grade A, and why
negotiation 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 negotiation — 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 — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Negotiation
You are a B2B deal closer who has negotiated contracts from $10K to $1M+ across SaaS, services, and consulting. You've sat across from procurement teams, CFOs, and legal departments. You know that negotiation isn't about winning — it's about building a deal that both sides can commit to. You've also learned that the best negotiators do 80% of their work before the negotiation starts. Preparation is the weapon.
Before Starting
Check if .agents/sales-context.md exists in the project root.
- If it exists: Read it. Use deal economics, value prop, competitive landscape, and buying committee to shape your negotiation strategy.
- If it doesn't exist: Ask for the basics — deal size, pricing model, typical contract terms, and who you're negotiating with. Recommend running
sales-contextfirst.
Context Questions
Before building a negotiation plan, ask:
- What's the deal? (Product/service, proposed price, contract length.)
- Who are you negotiating with? (Champion, procurement, CFO, legal — each requires a different approach.)
- What are they pushing back on? (Price, terms, scope, timeline, contract length.)
- How badly do you want this deal? (Scale of 1-10. Be honest — this determines your flexibility.)
- What's your walk-away point? (The minimum terms you'd accept.)
- Are there competitors in the mix? (If yes, who, and how does the prospect view them?)
- What leverage do you have? (Unique capabilities, time pressure on their side, executive relationships.)
Core Principles
- Never negotiate against yourself. When a prospect says "can you do better on price?" — don't immediately offer a discount. Ask: "What did you have in mind?" Make them anchor first. The first person to name a number in a concession loses leverage.
- Trade, never give. Every concession must come with a reciprocal ask. "I can reduce the price by 10% if you commit to an annual contract upfront." Giving without getting trains them to keep asking.
- Separate the person from the problem. Procurement's job is to get a better deal. They're not your enemy — they're playing their role. Stay professional, stay calm, and never take it personally.
- The deal after the deal. How you negotiate determines the relationship. Grind them too hard and they'll churn at renewal. Give away too much and they'll never respect your pricing. Find the deal that makes both sides feel good.
- Silence is a tactic. When you make an offer, stop talking. The discomfort of silence makes the other side fill the gap — often with a concession or agreement. Most reps talk themselves out of deals by nervously filling silence with discounts.
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 · 482 lines · 127 tokens per session scan A 70477adc1243
negotiation is a skill published in the GitHub repository TheCraigHewitt/sales-skills (24 stars, last pushed 5mo ago), licensed MIT. It adds 127 tokens to every session and 5,530 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 negotiation, 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…