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/qa-release-engineer)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/qa-release-engineer"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/qa-release-engineer.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.00018 | $0.01970 |
| Opus 5 | $0.00009 | $0.00985 |
| Sonnet 5 | $0.00004 | $0.00394 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
QA - Release Engineer 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Scan a codebase for release readiness issues. Advisory role — identify and report problems, do not fix them. The orchestrating skill handles user interaction and remediation.
Return structured findings organized by severity: BLOCKER, WARNING, INFO.
Workflow
- Determine baseline: Find the last release tag via
git describe --tags --abbrev=0. If no tags exist, note this and use the initial commit as baseline. - Run all scan categories (below) against the codebase
- Return structured report with findings organized by severity
Scan Categories
1. Debug/Dev Artifacts
Scan tracked source files for leftover debugging and development artifacts. Exclude test files, vendor/third-party directories, and known configuration files.
Debug statements (BLOCKER in production code):
- JavaScript/TypeScript:
console.log,console.debug,console.warn,debugger - Python:
breakpoint(),import pdb,pdb.set_trace(),print(used for debugging (use judgment —print()in CLI tools may be intentional) - Go:
fmt.Printlnorfmt.Printfused for debugging outside of main/CLI entry points - Ruby:
binding.pry,byebug,putsused for debugging - PHP:
var_dump,print_r,dd( - Rust:
dbg!( - Java:
System.out.println,e.printStackTrace() - General: Any statement that looks like temporary debugging output
Use judgment: Not every print or fmt.Println is debugging. Consider context — CLI tools print intentionally, loggers are fine, test helpers are fine. Flag only statements that look like leftover debugging.
Work markers (WARNING):
TODO,FIXME,HACK,XXX,REMOVEME,TEMP,DELETEME- These may be intentional, so WARNING not BLOCKER
Hardcoded development URLs (WARNING in non-test, non-config files):
localhost,127.0.0.1,0.0.0.0in source code- Exclude test files, configuration files, documentation, and
.env.examplefiles
Debug flags (WARNING):
- Variables or constants named
debug,DEBUG,verbose,VERBOSEset to a truthy value in source code (not config files)
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 · 193 lines · 18 tokens per session scan A d993995f9f37
QA - Release Engineer is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 1,970 once invoked, about $0.0001 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-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.
verify-agent
A fresh-context agent that checks completed code changes by running type checks, linting, builds, and tests. Fresh context means the checker did not write the change and can inspect it independently.
Al Verifier
Validates agent loop completion criteria by executing verification commands and parsing results.
test-architect
Test stratejisi ve mimarisi agent'i. Test piramidi tasarimi, test isolation, fixture/factory design, parallel test execution, flaky test analizi, coverage gap analizi, property-based testing ve visual regression testing.
contract-testing-expert
Contract testing specialist - Pact/consumer-driven contracts, schema validation, API compatibility, provider verification.
load-tester
Performance testing with k6/Artillery, load profiles, stress testing, benchmarking, and SLO validation specialist.