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-handle-incident/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-handle-incident)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-handle-incident"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-handle-incident/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/aget-framework/aget/aget-handle-incident"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-handle-incident.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 110 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00012 | $0.00589 |
| Opus 5 | $0.00006 | $0.00295 |
| Sonnet 5 | $0.00002 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
aget-handle-incident 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aget-handle-incident
Handle incidents including triage, diagnosis, mitigation, and resolution tracking. Maintains incident timeline and post-mortem documentation.
Instructions
When this skill is invoked:
-
Triage
- Assess severity (P1-P4)
- Identify impact scope
- Determine urgency
-
Diagnose
- Gather diagnostic information
- Identify probable causes
- Document findings
-
Mitigate
- Propose mitigation steps
- Prioritize by impact
- Execute with approval
-
Track
- Maintain timeline
- Document all actions
- Update status
-
Resolve & Learn
- Confirm resolution
- Document root cause
- Create prevention recommendations
Severity Classification
| Level | Criteria | Response |
|---|---|---|
| P1 | Complete outage, data loss | Immediate |
| P2 | Major feature broken | Within hour |
| P3 | Minor feature degraded | Within day |
| P4 | Cosmetic/minor | Scheduled |
Output Format
## Incident Report: [ID]
### Summary
| Field | Value |
|-------|-------|
| Severity | P[1-4] |
| Status | [Active/Mitigated/Resolved] |
| Impact | [Description] |
| Started | [Timestamp] |
| Resolved | [Timestamp or Ongoing] |
---
### Timeline
| Time | Event | Actor |
|------|-------|-------|
| [HH:MM] | [What happened] | [Who/What] |
---
### Diagnosis
**Probable Cause**: [Description]
**Evidence**:
- [Finding 1]
- [Finding 2]
---
### Mitigation
| Step | Action | Status |
|------|--------|--------|
| 1 | [Action] | [Done/Pending] |
| 2 | [Action] | [Done/Pending] |
---
### Root Cause Analysis (Post-Resolution)
**Root Cause**: [Description]
**Prevention**:
1. [Action to prevent recurrence]
Constraints
- C1: NEVER skip severity assessment — severity drives response priority
- C2: NEVER apply fixes without user approval — production changes require authorization
- C3: NEVER close incident without confirmation — premature closure hides ongoing issues
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 · 117 lines · 12 tokens per session scan A 0ef456aa8e85
aget-handle-incident is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 589 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-check-health
Run AGET health inspection and housekeeping checks. Detect-only — pair with /aget-enhance-health for remediation.
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-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818). Coverage and consistency mode.
aget-file-issue
File issues with L520 governance compliance.
aget-release-build
Execute gate deliverables with the Builder perspective of the Release Delivery Triad (L818). Speed-optimized execution mode.