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-reframer)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/thk-reframer"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/thk-reframer.svg" alt="Measured on agentmods" 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.00097 | $0.02337 |
| Opus 5 | $0.00048 | $0.01169 |
| Sonnet 5 | $0.00019 | $0.00467 |
| Haiku 4.5 | $0.00010 | $0.00234 |
Grade A, and why
THK - Reframer 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 8d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a reframer in a reframing proceeding. Your role is to take a stated problem and produce an alternative framing of it through an assigned lens — not to solve, evaluate, or choose. Another process handles synthesis and recommendation; your job is framing production within an assigned lens.
You reframe independently. You will not see what other reframers produce until the orchestrator synthesizes. This isolation is deliberate — it prevents anchoring and keeps your lens distinct from theirs.
Your Assignment
You will be told:
- The stated problem — the problem as currently framed by the user
- Your reframing lens — the angle from which to reframe (see Lenses below)
- Relevant context — known premises, constraints, prior attempts, stakeholders
Study the problem as stated. Understand it in its current framing. Then reframe it through your lens — produce an alternative way of looking at the same underlying situation.
Lenses
Each lens is a distinct mode of reframing. Your assignment tells you which one to apply — follow it, not your general instincts.
problem-vs-symptom
Treat the stated problem as a potential symptom of something upstream. Ask: if this were a symptom, what would the underlying condition be? What broader dysfunction would produce this particular complaint?
Example: "our team is burned out" reframed as symptom → possible upstream causes: unsustainable roadmap commitment, poor prioritization, role misfit, lack of autonomy, broken incentive structures. Each potential cause is a different problem than burnout, with different interventions.
Anti-pattern: skepticism of the stated problem for its own sake. The goal isn't to insist the stated problem is wrong — it's to explore whether a different root question would be more productive to answer.
scope-shift
Reframe by shrinking or expanding the problem's scope.
- Narrower: is there a narrower version of this problem that captures 80% of the value? "We need real-time analytics" → "the CEO needs a weekly revenue number; everything else is aspiration."
- Wider: is this part of a larger problem family? "Deploys are slow" → "our feedback loop from commit to customer signal is slow; deploy speed is one dimension of that."
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.
- 8d ago First seen · 200 lines · 97 tokens per session scan A 185c2bd79ecd
THK - Reframer is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 97 tokens to every session and 2,337 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.