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 sarturko-maker/Claude-Plugin-MCP --skill yolo-negotiationgit clone --depth 1 https://github.com/sarturko-maker/Claude-Plugin-MCPWrote 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/sarturko-maker/claude-plugin-mcp/yolo-negotiation)<a href="https://agentmods.dev/skills/sarturko-maker/claude-plugin-mcp/yolo-negotiation"><img src="https://agentmods.dev/badge/skills/sarturko-maker/claude-plugin-mcp/yolo-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/sarturko-maker/claude-plugin-mcp/yolo-negotiation"><img src="https://agentmods.dev/badge/skills/sarturko-maker/claude-plugin-mcp/yolo-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.00050 | $0.01189 |
| Opus 5 | $0.00025 | $0.00594 |
| Sonnet 5 | $0.00010 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
yolo-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 10d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Contract Negotiation
Full-autonomy negotiation command. Same negotiation logic as /negotiate but
with all checkpoints removed. Claude reads the document, makes every decision
autonomously, and executes the full pipeline without stopping.
Configuration files (persona, authority, playbook) are still loaded and used to inform Claude's judgment -- they shape decision quality but never gate execution.
Step 1: Gather Context
From the user's message, determine:
- Document path -- must be a
.docxfile - Instructions -- what the user wants (brief or detailed)
- Client author name -- for Track Changes attribution. Infer from config or the user's message. If unclear, ask once.
- Client role -- buyer, seller, landlord, etc. Infer from the instructions or document context.
Do NOT run a multi-step wizard. Extract what you can from the initial message. If something critical is missing, ask in one follow-up at most.
Step 2: Load Configuration
Follow the negotiate-contract skill's Step 1 for configuration loading. The three-level fallback applies:
- Project directory --
PERSONA.md,AUTHORITY.md,PLAYBOOK-*.md,LOA.mdin the current working directory - Global config --
~/.config/claude-negotiator/ - Shipped defaults -- the plugin's
defaults/directory
If no custom config exists, the defaults work out of the box. Users can
customise behaviour by placing PERSONA.md, AUTHORITY.md, or
PLAYBOOK-*.md files in their project directory or
~/.config/claude-negotiator/.
Step 3: Ingest and Detect
Call the ingest_document MCP tool with the document path. Then determine the
document type by checking the annotated text for CriticMarkup tracked change
markers:
- No
{++or{--markers -- this is a clean document. A document with only comment markers ({>>) but no tracked change markers is also treated as clean. {++or{--markers present -- this document has existing tracked changes.
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.
- 10d ago First seen · 121 lines · 50 tokens per session scan A a770e236f8c6
yolo-negotiation is a skill published in the GitHub repository sarturko-maker/Claude-Plugin-MCP (14 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 1,189 once invoked, about $0.0003 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
html-ppt-zhangzara-stencil-tablet
A workplace-safety compliance review for a manufacturing regulator — findings, the evidence chain, and the corrective mandate. Built as a decision-grade policy briefing deck for regulator, plant leadership.
treatment-plans
Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and…
handbook-updates
Diff a proposed handbook change against the current version, flag ripple effects and state supplement impacts. Use when user says "update the handbook", "add this to the handbook", "handbook change", or has a policy ready for insertion.
software-copyright-materials
A workflow for creating Chinese application materials for software copyright registration from a real software project.
iflytek-contract-intelligence-review
A contract-review workflow for scanned or digital agreements. It can recognize document text, examine clauses, detect risks, check compliance, and create translation summaries; its output is for review and is not formal legal advice.
legal-writer
Legal document drafting -- contracts, memos, briefs, complaints, demand letters, opinions, discovery, settlements, ToS, privacy policies. Full pipeline: document structure, per-section writing, Bluebook citation, case law lookup (CourtListener API), regulation lookup (eCFR API), DOCX output, and TDD-style verification…