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 on-deck-society/love-stack --skill escalationgit clone --depth 1 https://github.com/on-deck-society/love-stackWrote 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/on-deck-society/love-stack/escalation)<a href="https://agentmods.dev/skills/on-deck-society/love-stack/escalation"><img src="https://agentmods.dev/badge/skills/on-deck-society/love-stack/escalation/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/on-deck-society/love-stack/escalation"><img src="https://agentmods.dev/badge/skills/on-deck-society/love-stack/escalation.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.00027 | $0.00477 |
| Opus 5.5 | $0.00011 | $0.00191 |
| Sonnet 5.5 | $0.00005 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
escalation 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 1mo 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.
What it actually says
Escalation
When activated, help the user draft a message or conversation plan for a situation that requires pushing back, disagreeing, renegotiating, or escalating.
The Framework
Every escalation message should have four components:
- Acknowledge: State you understand their position or the current state without conceding.
- Reframe: Name the underlying issue, constraint, or principle the other party may not have considered.
- Propose: Offer a specific alternative, ask, or next step.
- Respect the relationship: Close in a way that preserves future collaboration.
Escalation Levels
Calibrate tone to the situation. Ask the user which level applies if unclear:
- Level 1 (Low stakes, first attempt): Warm, collaborative, "I might be missing something" framing.
- Level 2 (Mid stakes, second attempt): Direct but diplomatic. Acknowledge the prior exchange. State the disconnect clearly.
- Level 3 (High stakes, final attempt): Formal. State the consequences of continued impasse. Propose a specific path forward or a specific exit.
- Level 4 (Formal escalation): Document-the-record tone. Cc the right people. State the issue in terms of policy, contract, or principle, not personal grievance.
What to Avoid
- Ultimatums without a real alternative
- Personal attacks or character framing
- Passive aggression ("per my last email", "as discussed")
- Apologies that weaken the position ("sorry to bother")
- Hedging that obscures the ask
Output
Produce:
- The message itself, at the calibrated level
- One-line summary of the strategic intent
- Optional: a "if they push back" follow-up draft
When to Invoke
Invoke when the user says: "help me push back", "I need to escalate this", "write a disagreement email", "how do I tell them no", "I want to renegotiate", or describes a professional conflict they need to respond to.
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.
- 1mo ago First seen · 49 lines · 27 tokens per session scan A 5d67fdcca6db
escalation is a skill published in the GitHub repository on-deck-society/love-stack (5 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 477 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…