Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Edmonds-Commerce-Limited/claude-code-hooks-daemonnpx agentmods add agents/edmonds-commerce-limited/claude-code-hooks-daemon/transcript-inspectorWrote 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/agents/edmonds-commerce-limited/claude-code-hooks-daemon/transcript-inspector)<a href="https://agentmods.dev/agents/edmonds-commerce-limited/claude-code-hooks-daemon/transcript-inspector"><img src="https://agentmods.dev/badge/agents/edmonds-commerce-limited/claude-code-hooks-daemon/transcript-inspector/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/agents/edmonds-commerce-limited/claude-code-hooks-daemon/transcript-inspector"><img src="https://agentmods.dev/badge/agents/edmonds-commerce-limited/claude-code-hooks-daemon/transcript-inspector.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.00049 | $0.03261 |
| Opus 5.5 | $0.00020 | $0.01304 |
| Sonnet 5.5 | $0.00010 | $0.00652 |
| Haiku 4.5 | $0.00005 | $0.00326 |
Grade A, and why
transcript-inspector 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 21d 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.
How it starts
The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transcript Inspector - Stop Hook Dogfooding Diagnostics
Purpose
Diagnose stop hook failures by reading Claude Code session transcripts and cross-referencing with daemon logs. Primary use case: "Claude stopped when it should have been blocked" or "the stop hook isn't working."
How to Use This Agent
Invoke when:
- Claude stops without a
STOPPING BECAUSE:prefix and the daemon did not block it - A user had to type "go" or "continue" manually (symptom of broken stop hook)
preventedContinuation: falseappears in transcript when it should betrue- Any stop hook dogfooding regression
Step 1: Find the Current Transcript
# List all transcript files for this project, sorted by modification time (newest last)
ls -lt /root/.claude/projects/-workspace/*.jsonl 2>/dev/null | head -5
# The most recent file is the current session
TRANSCRIPT=$(ls -t /root/.claude/projects/-workspace/*.jsonl 2>/dev/null | head -1)
echo "Transcript: $TRANSCRIPT"
The project path encoding: /workspace → -workspace. If running from a different path, adjust accordingly.
Step 2: Locate stop_hook_summary Entries
These are the definitive outcome records for every stop hook invocation.
#!/usr/bin/env python3
import json
import sys
transcript = sys.argv[1] # pass transcript path as arg
with open(transcript) as f:
lines = f.readlines()
print(f"Total lines: {len(lines)}\n")
for i, line in enumerate(lines):
try:
e = json.loads(line)
except json.JSONDecodeError:
continue
# Stop hook outcome record
if e.get('subtype') == 'stop_hook_summary':
print(f"Line {i}: stop_hook_summary")
print(f" preventedContinuation : {e.get('preventedContinuation')}")
print(f" level : {e.get('level')}")
print(f" hasOutput : {e.get('hasOutput')}")
print(f" hookErrors : {e.get('hookErrors')}")
print(f" raw : {json.dumps(e, indent=2)}")
print()
# Stop hook progress event (hook firing)
if (e.get('type') == 'progress'
and isinstance(e.get('data'), dict)
and e['data'].get('type') == 'hook_progress'
and e['data'].get('hookEvent') == 'Stop'):
print(f"Line {i}: Stop hook FIRING (progress event)")
print(f" hookName : {e['data'].get('hookName')}")
print(f" toolUseID: {e.get('toolUseID')}")
print()
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.
- 21d ago Changed · +6 lines d4d9223928f1
- 1mo ago First seen · 347 lines · 49 tokens per session scan A 06d77bc0d486
transcript-inspector is an agent published in the GitHub repository Edmonds-Commerce-Limited/claude-code-hooks-daemon (4 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 3,261 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-08-31.
Other agents, from other repositories
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
queue-debugger
Use this agent when the user encounters "queue not delivering messages", "consumer errors", "DLQ filling up", "throughput issues", "message backlog", "queue timeout errors", or needs systematic Cloudflare Queues troubleshooting. Examples.
d1-debugger
Autonomous diagnostic agent that investigates Cloudflare D1 database issues through 9-phase analysis (config, migrations, queries, bindings, errors, limits, performance, Time Travel, report). Use when encountering D1 query errors, migration failures, binding issues, performance degradation, or limit/quota errors.
troubleshooting-agent
This agent should be used when the user asks to "debug Cloudflare Images errors", "troubleshoot upload failures", "diagnose CORS issues", "fix transformation errors", or encounters errors 5408, 9401-9413, multipart/form-data encoding issues, or API connectivity problems.
cors-debugger
Use this agent when the user encounters "CORS errors", "browser upload fails", "access-control-allow-origin", "CORS policy blocked", or needs CORS troubleshooting. Examples.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.