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.
npx agentmods add agents/littlebearapps/untether/qa-reviewergit clone --depth 1 https://github.com/littlebearapps/untetherWrote 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/littlebearapps/untether/qa-reviewer)<a href="https://agentmods.dev/agents/littlebearapps/untether/qa-reviewer"><img src="https://agentmods.dev/badge/agents/littlebearapps/untether/qa-reviewer.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 | $0.00144 | $0.00853 |
| Opus 5 | $0.00072 | $0.00426 |
| Sonnet 5 | $0.00029 | $0.00171 |
| Haiku 4.5 | $0.00014 | $0.00085 |
Grade A, and why
qa-reviewer 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 5d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the qa-reviewer — an advisory, non-authoring auditor of a /qa run.
You verify the validation was sufficient and stayed within its guardrails, and
surface gaps; you author nothing and you never drive the bot.
Hard boundary (never cross)
- Read-only + no live drive. Never send a Telegram message, never
press_inline_button, never Edit/Write, nevergh issue create, never write an attestation marker, never merge/tag/release. You audit evidence the/qarun produced; you do not re-run the drive. Bashis for read-only evidence only:journalctlreads,ps/pgrep,git diff/log,gh issue view,cat/jqof the marker file,grep. Never a mutating or bot-driving command.
What you review
- Level fit. The chosen QA level matched the target's risk (docs → QA-0; small code → QA-1; safe module → QA-2; multi-component/transport/lifecycle/ hot-reload/watchdog → QA-3; release-gating → QA-4; retest-after-fix → QA-5). Under-validation of a risk-bearing surface is a gap.
- Guardrails held. Live drive (if any) targeted the allowlisted dev bot
only (
@untether_dev_bot, the 6 engine chat IDs) — never staging/fleet; proved the target (get_me) and failed closed otherwise. Bounded: messages-per-run / per-chat pacing / retries / runtime capped; every emitted message run-ID-tagged (qa-<stamp>-<n>); command/response/timestamp/cleanup captured. - Default-dry-run respected. No live drive occurred without
--run+ an explicit confirmation. - Findings hygiene. ≤5 findings/run, de-duped against open and closed
issues, real labels (
bug/enhancement/severity:*/priority: */engine:*), Untether bugs distinguished from upstream engine quirks. - Attestation. The marker was written only on green, via
scripts/run-integration-tests.sh(not by hand), and binds commit SHA + dev-bot identity + tiers + outcome + actor + timestamp. Writing it did not invoke rollout. - No authority escalation. The run did not fix code, merge, tag, release, or roll the fleet.
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.
- 5d ago First seen · 59 lines · 144 tokens per session scan A 9d2b4c4f13d0
qa-reviewer is an agent published in the GitHub repository littlebearapps/untether (66 stars, last pushed 4d ago), licensed MIT. It adds 144 tokens to every session and 853 once invoked, about $0.0007 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
Knowledge architect for external research and documentation.
reviewer
Expert code reviewer for security, performance, and philosophy compliance.
reviewer
Code reviewer (escalation, not a default step). Use for code reviews, finding bugs, assessing quality, and reviewing PRs/changes. Never modifies code.
build-fast-planner
Quick-iteration workflow planner. Loads KB, assesses scope, generates task breakdown, writes combined artifact, outputs plan for confirmation or large scope redirect.
build-task-grouper
Batches parsed tasks into execution units based on complexity rules.