agentmods.dev

set-copilot: Command for Claude Code

.claude/commands/set/forensics.md

forensics is a command for Claude Code from tatargabor/set-copilot. It costs 0 tokens per session (819 once invoked), scanned A, a copy of forensics, MIT.

A forensic analysis command for examining a completed multi-agent orchestration run, including its logs and session records.

In plain words
What is it for?
It helps find what went wrong in a finished run and identify the sessions that need investigation.
Why use it?
It narrows large log files to errors, failed commands, interruptions, permission problems, and possible crashes before deeper inspection.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

This is tatargabor/set-copilot's own configuration. It tells Claude Code how to work on set-copilot 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 set-copilot configures →

not rated 3repo 20d ago A scan 0 tokens copy · 100% MIT
View source ↗ tatargabor/set-copilot
Reuse

Borrowing it

Nothing to install: this file belongs to tatargabor/set-copilot. 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/tatargabor/set-copilot/master/.claude/commands/set/forensics.md
Clone the repo
git clone --depth 1 https://github.com/tatargabor/set-copilot

Made for: Claude Code.

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 forensics

README.md
[![agentmods](https://agentmods.dev/badge/commands/tatargabor/set-copilot/forensics/github.svg)](https://agentmods.dev/commands/tatargabor/set-copilot/forensics)
Your own site
<a href="https://agentmods.dev/commands/tatargabor/set-copilot/forensics"><img src="https://agentmods.dev/badge/commands/tatargabor/set-copilot/forensics/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 forensics

Your own site · 80×15
<a href="https://agentmods.dev/commands/tatargabor/set-copilot/forensics"><img src="https://agentmods.dev/badge/commands/tatargabor/set-copilot/forensics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 819 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 100% copy Near-identical to another mod 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.00000 $0.00819
Opus 5.5 $0.00000 $0.00328
Sonnet 5.5 $0.00000 $0.00164
Haiku 4.5 $0.00000 $0.00082

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

Security

Grade A, and why

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

Origin

This is a copy

100% identical to forensics — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/set/forensics.md · 72 lines

How it starts

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

Forensic analysis of a completed orchestration run.

Input: <run-id> (the e2e-runs directory name, e.g. craftbrew-run-20260421-0025). If omitted, ask the user which run to analyse.

You are debugging a completed orchestration run. Use set-run-logs to surface filtered views over Claude Code session transcripts + orchestration logs without dragging raw 300+ KB jsonl files into context.

CRITICAL: never read raw session jsonl unbounded

A single session jsonl can exceed 300 KB; a run has 50+ sessions. Always use the CLI's filtered views FIRST. Only fall back to Read on a specific line range after the CLI has narrowed the suspect.

Triage flow (follow in order)

  1. Discover:

    set-run-logs <run-id> discover

    Confirms which session dirs (main + each worktree) and orchestration artifacts were found.

  2. Digest — get the error map:

    set-run-logs <run-id> digest

    Aggregates tool_error, bash_nonzero_exit, stop_reason_anomaly, user_interrupt, permission_denial, and crash_suspect signals across every session, grouped by change → session → tool with snippets and counts.

  3. Drill into suspect sessions — for each suspect from the digest:

    set-run-logs <run-id> session <uuid-prefix> --errors-only

    The UUID prefix from the digest (e.g. 531d481b) is enough — minimum 6 chars. Use --tool <Bash|Edit|Read|...> to narrow further.

  4. Targeted probes — when a specific error signature matters:

    set-run-logs <run-id> grep "<pattern>"
set-run-logs <run-id> grep "EACCES" --tool Bash
set-run-logs <run-id> grep "MaxToken" -i --limit 100

    Emits only the matching message.content text, never raw jsonl. Default cap is 50 matches — raise with --limit only when you must.

  5. Cross-reference orchestration timing:

    set-run-logs <run-id> orchestration

    Per-change dispatch counts, last gate status, terminal status (e.g. MERGE_SUCCESS, FIX_ISS_ESCALATED), gate-outcome totals. Use this to map a suspect session back to the engine's view.

Read the full file on GitHub · 72 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 · 72 lines · 0 tokens per session scan A 32faa7ce0bd1

Subscribe to this mod's changes

forensics is a command published in the GitHub repository tatargabor/set-copilot (3 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 819 tokens. A static security scan graded it A with 0 findings. It is 100% identical to forensics, differing in 0 lines, and is treated as a copy.

Debugging
Related

Other commands, from other repositories

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

react-native

Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.

getsentry/toolkit · 0 tokens

auditar-cascading

Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.

luanpdd/kit-mcp · 54 tokens

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

http-service

Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.

MadAppGang/magus · 27 tokens

doctor

Badi configuration validation. Checks all Badi components and produces a diagnostic report.

fatihkan/badi · 0 tokens