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 ianklassen/pm-skills --skill escalation-judgmentgit clone --depth 1 https://github.com/ianklassen/pm-skillsWrote 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/ianklassen/pm-skills/escalation-judgment)<a href="https://agentmods.dev/skills/ianklassen/pm-skills/escalation-judgment"><img src="https://agentmods.dev/badge/skills/ianklassen/pm-skills/escalation-judgment/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/ianklassen/pm-skills/escalation-judgment"><img src="https://agentmods.dev/badge/skills/ianklassen/pm-skills/escalation-judgment.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.00092 | $0.00884 |
| Opus 5 | $0.00046 | $0.00442 |
| Sonnet 5 | $0.00018 | $0.00177 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
escalation-judgment 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Escalation Judgment
The judgment this encodes
Escalating too much makes you the PM whose Slack messages to leadership get skimmed. Escalating too little makes you the PM who sat on a risk that blew up a launch. Both failure modes look like "good instincts" from the inside in the moment. This skill is for catching yourself in either direction.
The decision framework
1. Is this a resource conflict, a decision you lack authority to make, or a genuine ambiguity? Or is it just hard?
Escalation is for moving something that's stuck because it needs someone else's authority or information, not for things that are merely difficult or annoying to resolve yourself. "This is hard and I want it to be someone else's problem" is a real feeling and not, on its own, a reason to escalate.
2. Have you tried the working-level path first, and can you say so?
A leader hearing an escalation will almost always ask "what have you tried?" If the honest answer is "nothing yet," you're not ready: go try the direct conversation, the async doc, the peer negotiation first. Escalating past that step burns credibility and also often turns out to be unnecessary once the direct conversation happens.
3. What is the actual cost of the delay this would cause if you wait one more cycle?
Some things genuinely can't wait for the next 1:1 or staff meeting (a launch-blocking legal question, a security issue, a customer commitment about to be broken). Most things can wait slightly longer than they feel like they can. Name the concrete cost of waiting; if you can't, you probably can wait.
4. Are you escalating the problem, or the emotion about the problem?
A frustrating stakeholder interaction and a genuine project risk can feel identical in the moment. Before escalating, separate what's actually blocking the work from what's just aggravating to deal with. Escalate the former; find another outlet (a peer, a skip-level 1:1, venting to a friend) for the latter.
Fast reference
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 · 58 lines · 92 tokens per session scan A e6bbc9f3c1c7
escalation-judgment is a skill published in the GitHub repository ianklassen/pm-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 884 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-08-31.
Other skills, from other repositories
utility-pm-skill-builder
Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions. Runs gap analysis, validates through a Why Gate, classifies by type and phase, generates draft files, and writes to a staging area for review before promotion.
utility-pm-skill-iterate
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
tool-note-and-vote
Structured group-decision mechanic that captures silent ideation, voting summaries, and Decider sign-off in a single bundled artifact. Use when a small team needs to make a fast decision with diverse input, when groupthink is a risk, or when a workshop moment demands silent contribution before discussion. Applicable…
utility-pm-workflow-builder
Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review. Runs overlap analysis against the existing workflows with a Why Gate, then helps select and sequence skills with authored…
foundation-prioritized-action-plan
Produce a comprehensive, evidence-grounded prioritized action plan from any PM input (notes, transcripts, drafts, executive asks, Slack threads, or a raw situation). Outputs one saveable document with an executive summary, input mirror, situation classification (Cynefin), the binding constraint (Theory of…
foundation-meeting-synthesize
Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting. Shows how decisions evolved, who has been saying what, where threads are stalling, and where contradictions have emerged. Produces a plain-text timeline, themes with…