verdict-dfir: Instructions file for Claude Code

AGENTS.md

verdict-dfir AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from TimothyVang/verdict-dfir. It costs 3,098 tokens per session, scanned A, original, Apache-2.0.

An AGENTS.md instruction file for a digital forensics and incident response project. Digital forensics examines electronic evidence, while incident response investigates and contains security incidents.

In plain words
What is it for?
Use it to guide agents working on the VERDICT forensic toolkit, its runtime, evidence tools, and custody records.
Why use it?
It explains the roles of the project's repositories and the safeguards that coding agents must follow when working with forensic evidence.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: $CLAUDE_PROJECT_DIR variable, but also the file is AGENTS.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is TimothyVang/verdict-dfir's own configuration. It tells Claude Code, Codex and OpenCode how to work on verdict-dfir itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything verdict-dfir configures →

Reuse

Borrowing it

Nothing to install: this file belongs to TimothyVang/verdict-dfir. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/TimothyVang/verdict-dfir/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/TimothyVang/verdict-dfir

Made for: Claude Code, Codex, OpenCode.

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.

agentmods badge for verdict-dfir AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/timothyvang/verdict-dfir/agents-md/github.svg)](https://agentmods.dev/instructions/timothyvang/verdict-dfir/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/timothyvang/verdict-dfir/agents-md"><img src="https://agentmods.dev/badge/instructions/timothyvang/verdict-dfir/agents-md/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.

agentmods 80×15 button for verdict-dfir AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/timothyvang/verdict-dfir/agents-md"><img src="https://agentmods.dev/badge/instructions/timothyvang/verdict-dfir/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,098 This file is loaded in full into every session.
When invoked 3,098 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.03098 $0.03098
Opus 5.5 $0.01239 $0.01239
Sonnet 5.5 $0.00620 $0.00620
Haiku 4.5 $0.00310 $0.00310

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

Security

Grade A, and why

verdict-dfir AGENTS.md 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.

AGENTS.md · 170 lines

How it starts

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

AGENTS.md

Agent instructions for VERDICT DFIR. This file is for Codex, OpenCode, and other coding agents that follow the AGENTS.md convention. Claude Code also reads CLAUDE.md; for Claude-specific runtime behavior, CLAUDE.md is authoritative.

VERDICT ecosystem — what is what

VERDICT is a local-first DFIR (digital forensics & incident response) agent platform, split into three repos:

Repo Role It is…
caseforge-core Headless controller: privacy routing, model selection, structured findings, custody validation, the caseforge CLI. the driver
verdict-opencode The agent runtime — a branded fork of opencode; the verdict binary is built from it. the engine
verdict-dfir-beta / this repo The forensic toolkit: findevil-mcp (Rust, 32 read-only tools) + findevil-agent-mcp (Python, 14 custody/crypto tools) + DFIR doctrine (agent-config/) + hash-chained custody. Consumed by caseforge via VERDICT_DFIR_HOME. the evidence lab (you are here)

Runtime flow: caseforge (controls + guards) → verdict binary (runs the agent) → this repo's findevil MCP tools (do the forensics) → hash-chained custody → caseforge verify.

Two rules everything obeys: the LLM is not the forensic source of truth (findings must cite a tool_call_id + output_sha256 + verified manifest); real evidence stays local by default.

Start Here

  • Work from the repository root.
  • Install or verify prerequisites with bash scripts/setup; use bash scripts/doctor.sh for a preflight summary.
  • The canonical product run is scripts/verdict <evidence>.
  • In Claude Code, the equivalent operator shortcut is /verdict <evidence> or investigate <path>.
  • Do not create or revive a separate Product CLI. scripts/verdict, scripts/find-evil, and Claude Code are the supported entry points.
  • Before changing investigation behavior, read CLAUDE.md and the runtime files in agent-config/.

Read the full file on GitHub · 170 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.

  1. 1mo ago First seen · 170 lines · 3,098 tokens per session scan A 0a13617118f1

Subscribe to this mod's changes

verdict-dfir AGENTS.md is an instructions file published in the GitHub repository TimothyVang/verdict-dfir (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3,098 tokens to every session, about $0.0124 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-04.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens