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 Miosa-osa/OSA --skill incident-responsegit clone --depth 1 https://github.com/Miosa-osa/OSAWrote 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/miosa-osa/osa/incident-response)<a href="https://agentmods.dev/skills/miosa-osa/osa/incident-response"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/incident-response/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/miosa-osa/osa/incident-response"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/incident-response.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.00040 | $0.00440 |
| Opus 5.5 | $0.00016 | $0.00176 |
| Sonnet 5.5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
incident-response 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
Incident Response
Workflow
- Record incident scope, time window, source systems, owner, and observed impact. Separate confirmed evidence from hypotheses.
- Preserve volatile observations and exported logs in a case directory; use hashes and collection timestamps. Read the acquisition example before collecting.
- Correlate identities, hosts and time; record clock skew and missing evidence. Do not treat an empty log as proof of no activity.
- Propose containment with concrete target, expected service impact and rollback. Execute changes only within the user's authorized scope; preserve recoverable access.
- Remove the confirmed cause, restore from validated state, rotate affected credentials where indicated, and monitor for recurrence.
- Verify normal service and the previously abused path; document evidence gaps and follow-up owners.
Worked example and prerequisites
Read references/workflow.md before execution. Use only registered OSA tools named in the frontmatter; command examples run through shell_execute. Check command -v for each external executable on the actual target. Optional packages, external collectors and vendor accounts are not bundled or presumed installed.
Evidence and completion
Return scope, prerequisites, exact checks, observed results, evidence paths, limitations, remediation, rollback and retest status. Mark unavailable checks as blocked or unverified. Preserve original evidence and report redacted copies where needed. Work within the authorized environment; do not silently expand to external targets.
Sources
Original OSA workflow and examples. Primary references are linked in the bundled workflow reference, so they remain available when this skill is installed separately. No third-party skill collection or rule pack is vendored.
What ships with it
2 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.
- 1mo ago First seen · 39 lines · 40 tokens per session scan A 3e6f607eeada
incident-response is a skill published in the GitHub repository Miosa-osa/OSA (78 stars, last pushed 11d ago), licensed Apache-2.0. It adds 40 tokens to every session and 440 once invoked, about $0.0002 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-09-15.
Other skills, from other repositories
unit-converter
Converts between common units of measurement including temperature, distance, and weight.
code-review
Reviews code changes for quality, security, and best practices.
tui-design
This skill should be used when designing terminal user interfaces, creating TUI layouts, choosing TUI color schemes, implementing keyboard navigation, building terminal dashboards, or working with any TUI framework. Activates on mentions of TUI design, terminal UI, Ratatui layout, Ink components, Textual widgets…
bun-development
Fast, modern JavaScript/TypeScript development with the Bun runtime, inspired by oven-sh/bun.
worker-mcp-orchestrator
Guides the coordinator agent on how to orchestrate, delegate to, and supervise local worker agents using the worker-mcp server.
clack
Build and maintain interactive Node.js/Bun CLIs with Clack (@clack/prompts and @clack/core). Use when an AI agent needs to design prompt flows, implement cancellation-safe input handling, add spinners/log/note UX, apply Clack best practices, or generate runnable examples aligned with official Clack docs.