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 OpenHands/extensions --skill incident-retrospectivegit clone --depth 1 https://github.com/OpenHands/extensionsWrote 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/openhands/extensions/incident-retrospective)<a href="https://agentmods.dev/skills/openhands/extensions/incident-retrospective"><img src="https://agentmods.dev/badge/skills/openhands/extensions/incident-retrospective/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/openhands/extensions/incident-retrospective"><img src="https://agentmods.dev/badge/skills/openhands/extensions/incident-retrospective.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 Data Exfiltration · line 78 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00055 | $0.00880 |
| Opus 5.5 | $0.00022 | $0.00352 |
| Sonnet 5.5 | $0.00011 | $0.00176 |
| Haiku 4.5 | $0.00006 | $0.00088 |
Grade A, and why
incident-retrospective scanned grade A with 1 finding 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 14d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "${OPENHANDS_HOST}/api/automation/v1/preset/prompt" \ How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Retrospective Drafter Automation
Set up an automation that drafts incident retrospectives by pulling data from Slack, Linear, and Notion.
Prerequisites
Required integrations
All three MCP integrations must be installed in Settings → MCP:
- Slack MCP — to gather incident-channel messages
- Linear MCP — to collect linked tickets and follow-ups
- Notion MCP — to publish the retrospective draft
Information to collect
Ask the user for:
- Incident identification — how are incidents identified? (e.g. Slack channel naming convention like
#inc-*, a Linear label, or manual trigger) - Slack channels — which channels contain incident chatter (e.g.
#incidents,#inc-*pattern) - Linear teams — which Linear teams/projects to inspect for follow-up tickets
- Retrospective template — what sections should the retro include? Default: Timeline, Impact, Root Cause, Action Items, Lessons Learned
- Notion destination — which Notion database or page should receive the draft
- Trigger type — manual dispatch, cron schedule, or triggered by an incident label being added
Setup Workflow
Step 1 — Verify MCP access
Test each integration:
Use the Slack MCP to list recent messages in an incident channel.
Use the Linear MCP to list recent issues for the target team.
Use the Notion MCP to search for the destination database.
If any fail, tell the user which integration needs to be installed first.
Step 2 — Determine trigger type
Ask the user how retros should be triggered:
- Manual — dispatch from the automations page when an incident wraps up
- Cron — run daily/weekly to check for recent incidents
- Event — triggered by a Linear label change or Slack message
Step 3 — Build the retro prompt
Construct a prompt that includes:
- How to identify the incident (channel pattern, label, etc.)
- Which Slack channels and Linear teams to query
- The retrospective template/sections
- Where to publish in Notion
What ships with it
5 files 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.
- 14d ago Changed aaf8c7ca5160
- 1mo ago First seen · 101 lines · 55 tokens per session scan A bf99ca3938e3
incident-retrospective is a skill published in the GitHub repository OpenHands/extensions (167 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 880 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…