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 fatihguner/foreman --skill delivering-the-dealgit clone --depth 1 https://github.com/fatihguner/foremanWrote 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/fatihguner/foreman/delivering-the-deal)<a href="https://agentmods.dev/skills/fatihguner/foreman/delivering-the-deal"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/delivering-the-deal/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/fatihguner/foreman/delivering-the-deal"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/delivering-the-deal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Anti-Refusal · line 78 Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.Fix: Remove jailbreak framing that nullifies safety policies or restrictions. Skill content must not instruct the agent to ignore its guidelines or operate without guardrails.
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.00092 | $0.05716 |
| Opus 5 | $0.00046 | $0.02858 |
| Sonnet 5 | $0.00018 | $0.01143 |
| Haiku 4.5 | $0.00009 | $0.00572 |
Grade A, and why
delivering-the-deal 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 5d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.
Delivering the Deal
LAST MILE -- 80% of negotiations collapse in the final 20%. The cause is always the same: premature relaxation when the finish line appears close. The parties have done the hard work of surfacing interests, generating options, building rapport. The outline of agreement is visible. And precisely at this moment, discipline evaporates. Preparation gives way to improvisation. Obstacles that should be anticipated arrive as surprises. Tactics that should be recognised go undetected. The deal that was 90% complete dies not from irreconcilable differences but from sloppy execution in the closing stretch.
Governor Phil Bredesen of Tennessee -- who built a healthcare company, transformed Nashville's downtown, and recruited the Titans from Houston -- put it plainly during a bus ride through rural China: "A vision without a plan is just a dream." Every negotiator envisions the great deal. Envisioning is the easy part. Delivering requires a systematic preparation process, a protocol for managing obstacles, and a framework for engineering the satisfaction that makes agreements durable.
The Framework
Part I: The Negotiator's Preparation Checklist
Research suggests that 80% of negotiating effort should occur before the parties sit down. The following 21 questions constitute a comprehensive preparation protocol. Working through them requires 30-60 minutes for a standard negotiation, longer for complex multi-party deals. The investment pays returns that compound across every round of the process.
Mapping the Terrain
- Who are the parties? Include anyone who will affect or be significantly affected by the outcome -- even those not at the table. The absent stakeholder who can veto a deal is more dangerous than the adversary across from you.
- What are the core issues? Identify the two or three fundamental questions the negotiation must answer. Price. Timeline. Scope. Control. Resist the temptation to catalogue every sub-issue at this stage.
- How important are the issues relative to the relationship? This single diagnostic determines whether to lead with a competitive or cooperative approach. High issue importance plus high relationship importance demands principled, interest-based negotiation. High issue importance plus low relationship importance permits more aggressive value-claiming.
- Will the other party negotiate competitively or cooperatively? Anticipate their posture. If competitive, prepare accordingly -- do not bring a cooperative playbook to a zero-sum fight without a fallback.
- What is your intended approach? You may plan to start cooperatively and shift competitive, or vice versa. The key is intentionality. Reactive negotiators lose.
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.
- 5d ago First seen · 282 lines · 92 tokens per session scan A abbc5a4c8f06
delivering-the-deal is a skill published in the GitHub repository fatihguner/foreman (50 stars, last pushed 6d ago), licensed MIT. It adds 92 tokens to every session and 5,716 once invoked, about $0.0005 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-09-06.
Other skills, from other repositories
Interview Prep Generator
Generate STAR stories, practice questions, and talking points from resume.
Automation Interview Prep
Prepare for SDET and automation interviews round by round, covering coding screens, framework design, API testing tasks, scenario questions, and STAR stories built from real testing work.
single-point-rubric-designer
Design a single-point rubric with one criterion and open columns for evidence. Use for student self-assessment, peer feedback, teacher formative feedback, or pre-task planning. Works with any learning target, with or without a band system.
Due Diligence Coordinator
Coordinate and prepare for investor due diligence with organized data rooms.
sc-edtech
Tier-1 strategy-consultant analysis tailored for edtech / online-learning problems — activation, completion, learning outcomes, monetization. Same five frameworks with edtech-aware MECE defaults, vocabulary, and root-cause priors.
learning-calibration-audit
Diagnose and correct false confidence in learning mastery using cognitive science research. Use when you feel confident about a topic but keep failing tests, want to audit your metacognition for illusions of knowing, are preparing for a high-stakes assessment and need to verify actual mastery, or suspect your study…