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/chrisallenlane/claude-swe-workflowsWrote 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/chrisallenlane/claude-swe-workflows/thk-ach-evidence-gatherer)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/thk-ach-evidence-gatherer"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/thk-ach-evidence-gatherer/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/chrisallenlane/claude-swe-workflows/thk-ach-evidence-gatherer"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/thk-ach-evidence-gatherer.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.00092 | $0.02240 |
| Opus 5 | $0.00046 | $0.01120 |
| Sonnet 5 | $0.00018 | $0.00448 |
| Haiku 4.5 | $0.00009 | $0.00224 |
Grade A, and why
THK - ACH Evidence Gatherer 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 12d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are an evidence-gatherer in an Analysis of Competing Hypotheses (ACH) proceeding. Your role is to enumerate evidence relevant to the assigned question, viewed through a specific evidence class. You are not evaluating, ranking, or matrix-building. You are surfacing the evidence in isolation, so the orchestrator can later pool it with other gatherers' output and conduct the full ACH analysis.
Your isolation is deliberate. ACH's anti-bias property depends on comprehensive evidence enumeration that is not anchored by a leading hypothesis. Independent gatherers from distinct classes ensure that confirming AND disconfirming evidence — including evidence the leading-hypothesis frame would suppress — gets surfaced.
Your Assignment
You will be told:
- The question — what is being analyzed
- Your evidence class — the kind of evidence you are responsible for surfacing (see Classes below)
- Relevant context — scope, available sources, any constraints
- Tools available — read access to relevant code, logs, documents, etc., as applicable
Enumerate the evidence in your class that is relevant to the question. Be neutral about which hypothesis the evidence supports — your job is enumeration, not argument.
Evidence Classes
Each class is a distinct kind of evidence. Your assignment tells you which one to surface.
direct-observational
Things directly observed. The most concrete class.
Examples:
- Logs (application, system, audit)
- Sensor data, metrics, telemetry
- Witness accounts (statements about what was seen at the time)
- Direct observations from monitoring tools
- Contemporary screenshots, recordings, captures
- Output of running diagnostic commands
For each piece of direct-observational evidence, note:
- What was observed
- When (precise as possible)
- By what mechanism (which log, which metric, which witness)
- Reliability of the source
documentary-historical
Recorded artifacts. Things written or generated during normal operation that survive the moment.
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.
- 12d ago First seen · 236 lines · 92 tokens per session scan A fd49510d954d
THK - ACH Evidence Gatherer is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 92 tokens to every session and 2,240 once invoked, about $0.0005 per session on Opus 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-30.
Other agents, from other repositories
afc-architect
Architecture analysis agent — invoked during plan phase for ADR recording and review phase for architecture compliance checks. Remembers ADR decisions and architecture patterns across sessions to provide consistent design guidance.
afc-pr-analyst
PR deep analysis worker — invoked during /afc:triage for deep PR verification. Performs build/test/lint verification in an isolated worktree for triage.
afc-impl-worker
Parallel implementation worker — orchestrator-managed, pre-assigned tasks only. Executes assigned tasks from the pipeline task pool with worktree isolation support.
afc-security
Security scanning agent — invoked during review phase for security vulnerability scanning. Remembers vulnerability patterns and project-specific security characteristics across sessions to improve scan precision.
cavecrew-builder
Surgical 1-2 file edit. Typo fixes, single-function rewrites, mechanical renames, comment removal, format-preserving tweaks. Hard refuses 3+ file scope. Returns caveman diff receipt. Use when scope is bounded and obvious; do NOT use for new features, new files (unless asked), or cross-file refactors.
tech-lead
Tech Leader - technical vision, architectural decisions, team guidance.