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 floomhq/moto --skill negotiatorgit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/negotiator)<a href="https://agentmods.dev/skills/floomhq/moto/negotiator"><img src="https://agentmods.dev/badge/skills/floomhq/moto/negotiator.svg" alt="Measured on agentmods" 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.00168 | $0.01063 |
| Opus 5 | $0.00084 | $0.00531 |
| Sonnet 5 | $0.00034 | $0.00213 |
| Haiku 4.5 | $0.00017 | $0.00106 |
Grade A, and why
negotiator 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 7d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Negotiator
Negotiation analysis and message crafting for high-stakes deals.
Core Workflow
1. Context Loading
Before any analysis, establish:
- Who are the parties? What's their relationship?
- What's been agreed so far? (look for written evidence: messages, emails, contracts)
- What's in dispute?
- What channel is this on? (WhatsApp = concise, email = structured, call = flexible)
- What's the timeline? (deadlines, meetings, external events)
Ask for context files if available. Look for negotiation tracking files in the working directory.
2. Mode Selection
Based on user request, operate in one of these modes:
ANALYZE - "analyze their position", "what do you think about this"
- Read counterparty's message/position
- Detect contradictions (compare across rounds)
- Identify position vs. interest (what they say vs. what they need)
- Assess power dynamics
- Flag emotional vs. rational arguments
- Output: structured analysis with actionable insights
SCORE - "score this", "review before I send", "is this good"
- Apply the 6-dimension scoring rubric (see references/framework.md)
- Information Leakage, Anchoring, Tone, Logic, Leverage, Trap Detection
- Score 1-10 per dimension + overall
- Flag specific phrases that are problematic
- Suggest concrete rewrites for flagged items
- Output: score card + specific fixes + rewritten version if below 8/10
DRAFT - "draft a response", "write a counter-offer"
- Structure: opening (tone-set) + substantive points + close
- Apply anchoring principles (concede from YOUR frame, not theirs)
- Run self-score before presenting
- Present draft + score + rationale for key choices
- Output: ready-to-send message + internal analysis
TRACK - "what have I conceded", "where do we stand"
- Build/update concession ledger across all rounds
- Calculate net position (given vs. received)
- Flag concession fatigue (giving more per round)
- Identify remaining leverage and room to move
- Output: concession table + strategic assessment
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.
- 7d ago First seen · 99 lines · 168 tokens per session scan A 751ddb2ebf3e
negotiator is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 168 tokens to every session and 1,063 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
afc:consult
Expert consultation — backend, infra, PM, design, marketing, legal, or tech guidance.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
memstack-business-contract-template
Use this skill when the user says 'contract', 'agreement', 'service agreement', 'NDA', 'freelance contract', 'consulting agreement', or needs service agreements with IP ownership, payment terms, and termination clauses. Do NOT use for invoicing or client onboarding.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
self-assessment
Interactive skill assessment with personalized learning path generation.