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 joaoguirunas/team-os --skill negotiationgit clone --depth 1 https://github.com/joaoguirunas/team-osWrote 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/joaoguirunas/team-os/negotiation)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/negotiation"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/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/joaoguirunas/team-os/negotiation"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/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.00077 | $0.04098 |
| Opus 5.5 | $0.00031 | $0.01639 |
| Sonnet 5.5 | $0.00015 | $0.00820 |
| Haiku 4.5 | $0.00008 | $0.00410 |
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 20d 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
97% identical to negotiation — 4 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Negotiation
Tactical empathy-based negotiation framework from FBI hostage negotiator Chris Voss. Understand the emotional drivers behind decisions and use proven techniques to build rapport, uncover hidden information, and reach better outcomes.
Core Principle
People want to be understood and feel safe. The most effective path to "yes" runs through empathy, active listening, and emotional intelligence -- not logic, arguments, or compromise. Treat every negotiation as a discovery process: your assumptions are hypotheses to test, and the other side's needs (respect, security, autonomy) matter more than their stated positions. Never split the difference -- no deal is better than a bad deal.
Scoring
Goal: 10/10. Score 1 point per satisfied Quick Diagnostic row (6 rows), plus up to 4 points for execution quality: emotions labeled out loud (+1), "That's right" earned not "You're right" (+1), no "Why?" / no splitting the difference / no chasing "yes" (+1), at least one Black Swan surfaced (+1). Bands: 9-10 = audit delivered, calibrated questions and BATNA prepared, "That's right" achieved, Black Swans hunted; 5-6 = some prep but arguing the position or chasing "yes"; <=3 = no audit, no BATNA, splitting the difference. Always state the current score and the specific gaps to reach 10/10.
Framework
1. Tactical Empathy
Core concept: Consciously imagine yourself in the counterpart's situation, then vocalize their perspective to create trust and openness.
Why it works: When people feel understood, brain chemistry shifts toward trust and cooperation, short-circuiting defensive reactions. Empathy is not agreement -- you can understand their position while advocating your own.
Key insights:
- Before responding, ask: "What is their world like right now?"
- Articulate their situation, pressures, and fears before stating your position
- Empathy must be genuine, not performed -- people detect fakeness instantly
- Unconditional positive regard: respect them as a person regardless of disagreement
- Emotions are contagious -- stay calm and positive; slow pace enables clear thinking
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.
- 20d ago Changed · +2 lines · -67 tokens per session 320655432548
- 1mo ago First seen · 295 lines · 144 tokens per session scan A f808051fc0c5
negotiation is a skill published in the GitHub repository joaoguirunas/team-os (4 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 4,098 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to negotiation, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
jsonl-log-analyzer
Analyze large JSONL log files using schema-aware partitioned analysis. Discovers field schema, generates tailored jq extraction recipes, and orchestrates parallel chunk analysts with synthesis. Use when processing JSONL logs exceeding context limits, performing log analytics, or investigating incident logs.
orchestration-patterns
Apply proven orchestration patterns for agent teams including parallel specialists, pipelines, swarms, research+implementation, plan approval, and multi-file refactoring. Use when choosing a team structure, designing workflows, or implementing specific coordination patterns.
task-system
Manage shared task lists for agent teams including creating tasks, setting dependencies, claiming work, and tracking progress. Use when creating work items, building task pipelines, coordinating task ownership, or managing task dependencies.
spawn-backends
Configure how teammate agents run including in-process, tmux, and iTerm2 backends. Use when choosing a display mode, setting up split panes, troubleshooting backend issues, or configuring teammateMode.
error-handling
Debug and recover from agent team errors including common errors, hooks for quality gates, known limitations, and recovery strategies. Use when encountering team errors, enforcing quality gates with hooks, understanding limitations, or debugging agent issues.
messaging
Send messages between agents using SendMessage including direct messages, broadcasts, shutdown requests/responses, and plan approvals. Use when communicating between agents, understanding message formats, or handling structured protocol messages.