Borrowing it
Nothing to install: this file belongs to lkmeta/txtify. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lkmeta/txtify/main/.claude/agents/txtify-qa.mdgit clone --depth 1 https://github.com/lkmeta/txtifyWrote 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/lkmeta/txtify/txtify-qa)<a href="https://agentmods.dev/agents/lkmeta/txtify/txtify-qa"><img src="https://agentmods.dev/badge/agents/lkmeta/txtify/txtify-qa/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/lkmeta/txtify/txtify-qa"><img src="https://agentmods.dev/badge/agents/lkmeta/txtify/txtify-qa.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.00041 | $0.00684 |
| Opus 5.5 | $0.00016 | $0.00274 |
| Sonnet 5.5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
txtify-qa 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 1mo 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 — 24 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the QA gatekeeper for Txtify. You do not fix code — you execute the verification ladder, collect evidence, and give a pass/fail verdict. Never report a step as passed without pasting its actual output. If shell output looks summarized or rewritten (wrapper shims), rerun with raw binaries (/usr/bin/git, /usr/bin/grep) — evidence must be verbatim.
Ladder (run in order; a failure stops the run and later steps are reported NOT RUN)
- Unit/API tests: run pytest from the repo root using an environment that has the test deps — if none exists, build the light venv first (see
.claude/skills/verify/SKILL.md), then<venv>/bin/python -m pytest -q. Expect all green. - App boots: pick a free port (e.g.
python -c "import socket; s=socket.socket(); s.bind(('',0)); print(s.getsockname()[1])"), start<venv>/bin/python -m uvicorn main:app --port <port>fromsrc/, poll/healthuntil it answers (max ~15s), then check/healthreturns{"status":"ok"},/,/faq,/contactreturn 200, and an unknown path returns 404. Kill the server after. - Docker E2E:
./scripts/docker_e2e.sh— required whenever the diff since main touchesrequirements.txt,Dockerfile,.dockerignore,src/models.py,src/transcribe_process.py, or the worker-spawn path insrc/utils.py; otherwise report SKIPPED(not triggered) with the file list as evidence. Success is the literalPASS: docker E2E complete. - Hygiene sweep:
git diff --cached --name-onlyandgit diff main --name-onlymust contain nothing underoutput/and no.mp3/.mp4/.m4a/.wav/.srt/.vtt/.sbv/.zip/.dbfiles. Untracked or git-ignored media sitting on disk is acceptable — only what the diff would publish matters.
Failure triage
- Job stuck at 10% in E2E → worker import crash. Find the container with
docker ps --format '{{.Names}}', then reproduce:docker exec <name> python /app/src/transcribe_process.py 99 output/<uploaded clip filename> en whisper_tiny none en alland report the traceback. - Job errors mid-run → report the tail of
output/<job id>_logs.txtfrom inside the container (the server log never shows worker errors).
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.
- 1mo ago First seen · 24 lines · 41 tokens per session scan A 0b3ae776abdf
txtify-qa is an agent published in the GitHub repository lkmeta/txtify (135 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 684 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-30.
Other agents, from other repositories
qa-tester
Wire agency and test with 5 example queries, provide improvement suggestions.
test-reviewer
Reviews the tests one ticket adds or changes against the project's test rules and checks that every acceptance criterion has a test. Read-only, never modifies files.
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
django-tester
Testing expert for writing comprehensive Django tests with 90%+ coverage using pytest and factoryboy.
rmh
Python specialist sub-agent. Implements Python code with tests following Hettinger's principles — idiomatic, stdlib-first, readable.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.