What is dfir-incident-toolkit?

A digital forensics and incident-response workflow for collecting and handling evidence after a security incident. It records file integrity, acquisition results, approval receipts for containment, rollback plans, and redaction of collected artifacts.

It is for read-only evidence collection, integrity recording, incident containment planning, rollback preparation, and redacting forensic artifacts.

It helps investigators preserve evidence and plan containment carefully without changing source data or exposing sensitive information unnecessarily.

dfir-incident-toolkit — Skill for Claude Code and Codex by Miosa-osa

Install

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.

Any agent

npx skills add Miosa-osa/OSA --skill dfir-incident-toolkit

Clone the repo

git clone --depth 1 https://github.com/Miosa-osa/OSA

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/miosa-osa/osa/dfir-incident-toolkit/github.svg)](https://agentmods.dev/skills/miosa-osa/osa/dfir-incident-toolkit)

Your own site

<a href="https://agentmods.dev/skills/miosa-osa/osa/dfir-incident-toolkit"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/dfir-incident-toolkit/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/miosa-osa/osa/dfir-incident-toolkit"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/dfir-incident-toolkit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,313 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00116	$0.01313
Opus 5.5	$0.00046	$0.00525
Sonnet 5.5	$0.00023	$0.00263
Haiku 4.5	$0.00012	$0.00131

Measured 1mo ago against content hash 93cc3283314c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dfir-incident-toolkit 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.

priv/skills/dfir-incident-toolkit/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DFIR — Incident Toolkit

Derived from T3MP3ST's src/dfir/toolkit.ts (Apache-2.0). Two disciplines make DFIR evidence usable: read-only acquisition (never alter what you investigate) and approved containment (never change a system without a preview, a digest, and a receipt).

1. Acquisition — read-only, verified, typed

Artifacts are collected by read-only collectors; the toolkit NEVER writes to the target during acquisition.
Every artifact becomes an evidence record: id, caseId, targetId, name, source, collectedAt, receivedAt, sha256, sizeBytes, collector, transfer, verified, redactedMetadata.
Integrity: hash at collection, re-verify on receipt (verified flag). A mismatch is a finding about your own pipeline.
Duplicate names within one acquisition are rejected — silent dedup loses evidence.
Metadata is redacted at acquisition (redactedMetadata), not at report time.
Outcomes are typed and final: collected | cancelled | permission-denied | collection-failed. permission-denied is a real result (record it, move on); it is not a retry candidate.

2. Containment — preview, digest, approval, receipt

Changing a compromised system is the most dangerous moment in IR. The pattern:

Preview the containment action first: {caseId, targetId, actionId, summary, rollback, commands[]} — the preview is hashed into a digest.
Approval is a separate record: {receiptId, caseId, targetId, actionId, previewDigest, approvedBy, approvedAt, expiresAt}. The approval binds to the EXACT digest of the previewed action — any change to the plan invalidates it.
Execution checks the binding: case/target/action IDs must match, the preview digest must match, the approval must not be expired, and approvedAt must precede execution start. Any mismatch → denied with authorization-required. No approval object at all → denied, always.
Receipt records the outcome: completed | partial | cancelled | denied | failed, with completedSteps/totalSteps and the rollback path attached.

Read the full file on GitHub · 104 lines

Changes

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 · 104 lines · 116 tokens per session scan A 93cc3283314c

Subscribe to this mod's changes

dfir-incident-toolkit is a skill published in the GitHub repository Miosa-osa/OSA (78 stars, last pushed 11d ago), licensed Apache-2.0. It adds 116 tokens to every session and 1,313 once invoked, about $0.0005 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-14.

LLM Security ai-agent elixir local-ai nanobot nanoclaw

unit-converter

Converts between common units of measurement including temperature, distance, and weight.

agentjido/jido_ai · 19 tokens

code-review

Reviews code changes for quality, security, and best practices.

agentjido/jido_ai · 15 tokens

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…

pass-agent/loomkin · 109 tokens

bun-development

Fast, modern JavaScript/TypeScript development with the Bun runtime, inspired by oven-sh/bun.

pass-agent/loomkin · 35 tokens

worker-mcp-orchestrator

Guides the coordinator agent on how to orchestrate, delegate to, and supervise local worker agents using the worker-mcp server.

noosxe/worker-mcp · 33 tokens

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.

pass-agent/loomkin · 72 tokens