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.
git clone --depth 1 https://github.com/spideynolove/claude-dotfilesWrote 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/commands/spideynolove/claude-dotfiles/forensics)<a href="https://agentmods.dev/commands/spideynolove/claude-dotfiles/forensics"><img src="https://agentmods.dev/badge/commands/spideynolove/claude-dotfiles/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.
<a href="https://agentmods.dev/commands/spideynolove/claude-dotfiles/forensics"><img src="https://agentmods.dev/badge/commands/spideynolove/claude-dotfiles/forensics.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.00014 | $0.00466 |
| Opus 5.5 | $0.00006 | $0.00186 |
| Sonnet 5.5 | $0.00003 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00047 |
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.
What it actually says
/forensics — Workflow Post-Mortem
Post-mortem investigation for stuck or failed workflows. Read-only — never modifies project files.
Step 1: Get Problem Description
If $ARGUMENTS is empty, ask: "What went wrong? e.g., 'got stuck on phase 3', 'plan execute failed silently', 'costs seem high'."
Step 2: Gather Evidence
# Commit timeline and frequency
git log --oneline -30
git log --format="%H %ai %s" -30
# Most-edited files (stuck-loop signal)
git log --name-only --format="" -20 | sort | uniq -c | sort -rn | head -20
# Uncommitted work (crash/interruption signal)
git status --short && git diff --stat
# Orphaned worktrees
git worktree list
Also read if they exist:
.planning/STATE.md— current position, blockers, last session.planning/ROADMAP.md— phase progress.planning/phases/*/— check for missing SUMMARY.md or VERIFICATION.md per phase
Step 3: Detect Anomalies
| Anomaly | Signal |
|---|---|
| Stuck loop | Same file in 3+ consecutive commits, similar messages |
| Missing artifact | Phase appears complete but no SUMMARY.md |
| Abandoned work | Large time gap + STATE.md shows "In progress" |
| Orphaned worktree | git worktree list path no longer active |
Step 4: Write Report
Save to .planning/forensics/report-TIMESTAMP.md:
# Forensics Report: [Problem]
**Date:** [timestamp]
**Confidence:** HIGH / MEDIUM / LOW
## Summary
[1-2 sentence diagnosis]
## Anomalies Found
- [TYPE] [description]
## Root Cause
[Most likely cause]
## Recommended Actions
1. [Action]
2. [Action]
Present report inline. Offer deeper investigation if needed.
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 · 69 lines · 14 tokens per session scan A c1e489f9b91e
forensics is a command published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 466 once invoked, about $0.0001 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-08-31.
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…
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.
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
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…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.