Borrowing it
Nothing to install: this file belongs to aget-framework/aget. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aget-framework/aget/main/.claude/skills/aget-escalate-issue/SKILL.mdgit clone --depth 1 https://github.com/aget-framework/agetWrote 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/aget-framework/aget/aget-escalate-issue)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-escalate-issue"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-escalate-issue.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.00669 |
| Opus 5 | $0.00007 | $0.00334 |
| Sonnet 5 | $0.00003 | $0.00134 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
aget-escalate-issue 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 8d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aget-escalate-issue
Escalate issues to higher authority when they exceed current scope. Creates structured escalation documentation.
Instructions
When this skill is invoked:
-
Verify Escalation Needed
- Confirm issue exceeds current authority
- Document why local resolution not possible
- Check if similar escalation exists
-
Document Context
- Issue description
- Impact assessment
- Prior attempts
-
Identify Target
- Appropriate escalation path
- Decision authority needed
- Contact method
-
Create Escalation
- Structured escalation document
- Urgency classification
- Tracking mechanism
Escalation Criteria
| Should Escalate | Should NOT Escalate |
|---|---|
| Exceeds authority | Within authority |
| Cross-portfolio | Single portfolio |
| Policy change | Operational |
| Resource conflict | Local resource |
| Security/compliance | Routine issue |
Output Format
## Escalation Request
### Issue Summary
| Field | Value |
|-------|-------|
| ID | ESC-[YYYY]-[NNN] |
| From | [Escalating Agent] |
| To | [Target Authority] |
| Date | [YYYY-MM-DD] |
| Urgency | [Low/Medium/High/Critical] |
---
### Issue Description
**Title**: [Brief title]
**Description**: [Full description of the issue]
**Impact**: [Who/what is affected, severity]
---
### Why Escalation Required
**Authority Check**:
- [ ] Issue exceeds my decision authority
- [ ] Requires cross-portfolio coordination
- [ ] Policy/governance decision needed
- [ ] Resource beyond my allocation
**Prior Attempts**:
1. [Attempt 1]: [Result]
2. [Attempt 2]: [Result]
---
### Request
**Decision Needed**: [Specific decision or action requested]
**Options** (if applicable):
1. [Option A]: [Pros/Cons]
2. [Option B]: [Pros/Cons]
**Recommendation**: [If you have one]
---
### Urgency Justification
**Urgency**: [Level]
**Why**: [Justification for urgency level]
**Deadline** (if any): [Date/Time]
---
### Tracking
**Escalation ID**: ESC-[YYYY]-[NNN]
**Status**: Open
**Created**: [Timestamp]
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.
- 8d ago First seen · 130 lines · 14 tokens per session scan A ee2ad73c77b9
aget-escalate-issue is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 669 once invoked, about $0.0001 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
aget-close-project
Close a PROJECTPLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECTPLAN…
aget-release-critique
Adversarial review with the Critic perspective of the Release Delivery Triad (L818). Dual-mandate: spec coverage audit + deep bug finding.
aget-file-issue
File issues with L520 governance compliance.
aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818). Coverage and consistency mode.
aget-release-build
Execute gate deliverables with the Builder perspective of the Release Delivery Triad (L818). Speed-optimized execution mode.
aget-propose-actions
Propose ranked next-best actions with evidence grounding, time budgets, and execute-all default. Formalizes the fleet's highest-frequency interaction pattern.