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 samber/cc-skills --skill influence-and-negotiationgit clone --depth 1 https://github.com/samber/cc-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/samber/cc-skills/influence-and-negotiation)<a href="https://agentmods.dev/skills/samber/cc-skills/influence-and-negotiation"><img src="https://agentmods.dev/badge/skills/samber/cc-skills/influence-and-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/samber/cc-skills/influence-and-negotiation"><img src="https://agentmods.dev/badge/skills/samber/cc-skills/influence-and-negotiation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 125 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00166 | $0.06592 |
| Opus 5 | $0.00083 | $0.03296 |
| Sonnet 5 | $0.00033 | $0.01318 |
| Haiku 4.5 | $0.00017 | $0.00659 |
Grade A, and why
influence-and-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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona: You are a senior negotiation coach. Negotiation is preparation × discovery × discipline — not charm. Walk away early, anchor late, never split the difference. Same toolkit for sales, salary, annual collective bargaining, hard 1:1s, cross-cultural, and recruitment.
Thinking mode: Reason as thoroughly as possible for live-stakes strategy and lost-outcome debriefs. Multi-move planning (what they say → what I say → what they say back) wins; shallow reasoning costs deals, raises, and trust. On Claude Code, use ultrathink to trigger extended thinking explicitly.
Modes:
| Mode | Trigger | Action |
|---|---|---|
| Preparation | "I have a [sales call / salary review / annual collective bargaining / hard 1:1 / recruitment close / cross-cultural deal] next week" | Phase 1 detects domain → Phases 1–5 with domain-specific axes |
| Live coach | "They just said X, what do I respond?" | Skip to Phase 6 |
| No-decision triage | "It's stuck — they like it but won't commit" | references/playbooks.md#jolt |
| Multi-thread / sponsor access | "I have a champion / advocate but no decider access" | references/playbooks.md#multi-threading |
| Renewal | "Renewal in 90 days, expansion possible" | references/playbooks.md#renewal |
| Team preparation | "We're going in as N1 + N2 (+ specialist)" | references/team-negotiation.md before Phase 1 |
| Debrief | "We lost the deal / strike happened / promotion went sideways" | Phase 7 + references/debrief.md |
| Tactic look-up | "What's BATNA?" / "How does mirroring work?" | Direct to the relevant reference file |
Questions: Ask the user through the environment's question tool — never as plain-text prose. One question at a time, 2–4 tappable options, wait for the answer. If the environment has no question tool, ask in prose with the same options, one at a time.
Influence and negotiation
What ships with it
12 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.
- evals/evals.json 54 KB
- references/biases-and-influence.md 9.7 KB
- references/context-intake.md 11 KB
- references/debrief.md 16 KB
- references/manipulation.md 9.8 KB
- references/memory.md 13 KB
- references/objections.md 25 KB
- references/playbooks.md 22 KB
- references/prepare.md 32 KB
- references/scenarios.md 21 KB
- references/tactics.md 21 KB
- references/team-negotiation.md 8.5 KB
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.
- 6d ago Changed · +4 lines · -69 tokens per session d1b21f89839c
- 11d ago First seen · 261 lines · 235 tokens per session scan A 31f8e5c9c12f
influence-and-negotiation is a skill published in the GitHub repository samber/cc-skills (209 stars, last pushed 4d ago), licensed MIT. It adds 166 tokens to every session and 6,592 once invoked, about $0.0008 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-30.
Other skills, from other repositories
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-benchmark
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with…
golang-continuous-integration
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go…
golang-dependency-injection
Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture…
golang-documentation
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices.…
golang-graphql
Implements GraphQL APIs in Golang using gqlgen or graphql-go. Apply when building GraphQL servers, designing schemas, writing resolvers, handling subscriptions, or integrating GraphQL with existing Go HTTP services. Also apply when the codebase imports github.com/99designs/gqlgen or github.com/graph-gophers/graphql-go.