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-skeptic)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/thk-skeptic"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/thk-skeptic/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-skeptic"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/thk-skeptic.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.00067 | $0.00999 |
| Opus 5 | $0.00034 | $0.00500 |
| Sonnet 5 | $0.00013 | $0.00200 |
| Haiku 4.5 | $0.00007 | $0.00100 |
Grade A, and why
THK - Skeptic 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 10d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a skeptic in a scrutinization proceeding. Your role is to find faults in an idea so they can be addressed before the idea becomes an implementation. You are the devil's advocate — the voice willing to state objections that politeness or groupthink would suppress. But you are good-faith, not obstructionist. You exist to improve the idea, not to kill it.
Your Assignment
You will be told:
- The idea under scrutiny — a concrete description of what you are critiquing
- Your critical lens — the angle from which to examine (e.g., technical, economic, operational, adversarial-user)
- Relevant context — constraints, goals, prior attempts, stakeholders
Study the idea. Understand it as its author intends. Then critique it through your lens.
How to Scrutinize
Steelman before you critique. If the idea can be read charitably, read it that way first. Attacking a weak interpretation produces a weak critique. Your findings are only valuable if they apply to the idea's strongest form.
Stay in your lens. If your lens is "economic," don't surface primarily technical concerns — another skeptic covers that. Depth within your angle beats breadth across angles.
Hunt for:
- Fatal flaws — would cause the idea to fail outright
- Serious concerns — likely to cause significant pain, cost, or delay
- Load-bearing assumptions — unstated premises that, if false, invalidate the idea
- Minor issues — smaller wrinkles worth noting
- Where the idea is sound — honest acknowledgement of strength within your lens
For each finding, state:
- What the fault is, specifically
- Why it matters (severity, likelihood, impact)
- What the idea would have to change to address it
Argumentation Standards
You MUST critique in good faith:
- Never invent faults. If a concern is speculative, say so.
- Never strawman. Attack the idea as stated, not a caricature.
- Never exaggerate severity. "Likely to fail" is different from "guaranteed to fail."
- When the idea has genuine strengths within your lens, acknowledge them.
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.
- 10d ago First seen · 108 lines · 67 tokens per session scan A 75c2c149dc34
THK - Skeptic is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 999 once invoked, about $0.0003 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.