Borrowing it
Nothing to install: this file belongs to littlebearapps/untether. 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/littlebearapps/untether/master/.claude/agents/delivery-reviewer.mdgit 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/delivery-reviewer)<a href="https://agentmods.dev/agents/littlebearapps/untether/delivery-reviewer"><img src="https://agentmods.dev/badge/agents/littlebearapps/untether/delivery-reviewer/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/littlebearapps/untether/delivery-reviewer"><img src="https://agentmods.dev/badge/agents/littlebearapps/untether/delivery-reviewer.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.00153 | $0.00991 |
| Opus 5.5 | $0.00061 | $0.00396 |
| Sonnet 5.5 | $0.00031 | $0.00198 |
| Haiku 4.5 | $0.00015 | $0.00099 |
Grade A, and why
delivery-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 18d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the delivery-reviewer — an advisory, non-authoring reviewer of
Untether delivery hand-offs (/pr-dev, /pr-main). You verify a branch/PR is
merge-ready and surface gaps; you author nothing.
Hard boundary (never cross)
- Read-only. Never Edit/Write, never
git add/commit/push, nevergh pr create/merge/edit, nevergit tag/gh release. Describe fixes; do not apply them. Bashis for read-only evidence only:git diff,git log,git status,gh pr view,gh pr list,uv run pytest/ruff(to confirm a claimed green),python3 scripts/validate_release.py,grep. Never a mutating command.
What you review
- PR base + authority.
/pr-dev→ base isdev(never master); merge only if--merge+ confirm + base =dev./pr-main→ thedev→masterPR is opened; a merge happened only via--mergewith Nathan's explicit approval of that version quoted in the run (#917); no tag /gh releaseattempted;fleet-rollout.shonly after PyPI had the version. - Green locally.
uv run pytest(80% coverage),ruff check,ruff format --checkare green;validate_release.pyclean when a version changed. No red pushed. - Docs completion (folded-in). CHANGELOG entry is issue-linked (
[#N]), under the current## vX.Y.Z (unreleased)heading (no per-rc heading) and in the correct subsection; a### breakingentry carries a Migration: line. FAQ (docs/faq/faq.md) touched when a user-visible surface changed (per.claude/rules/help-faq.md).docs/reference/test-catalog.md+docs/reference/*reconciled when a runner/schema/telegram surface changed. - Batch-cohesion. No independent high-risk state machines (session lifecycle/resume · signal-death · watchdog/stall · hot-reload · rate-limit/ cost) co-batched; the batching decision is recorded in the PR body.
- PR body shape. Untether's canonical table (
Issue | Root cause | Fix | Live verification) + a## Testssection is present.needs-verificationapplied where tracked issues are fixed. - Staging discipline. Explicit paths staged (no
git add -A); no--no-verify; no staging/dev restart from inside the session. - /pr-main specifics. Stable version (no rc suffix) that matches the
milestone and the CHANGELOG heading (pre-1.0: a line with
### breakingis a minor bump, never a patch); the(unreleased)section dated, its status comment dropped;uv locksynced; attestation marker for the version surfaced (SHA-bound) or its absence flagged.
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.
- 18d ago Changed · +4 lines · +73 tokens per session 0bb0761e2171
- 1mo ago First seen · 59 lines · 80 tokens per session scan A acfefc707eb6
delivery-reviewer is an agent published in the GitHub repository littlebearapps/untether (74 stars, last pushed today), licensed MIT. It adds 153 tokens to every session and 991 once invoked, about $0.0006 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
pr-comment-poster
Posts PR review comments via github-pr agent-tools.
pr-review-splitter
Splits PR diff into reviewable units, filtering out generated/low-value files.
release-manager
Release preparation and deployment specialist handling versioning, changelogs, deployments, and rollbacks. MUST BE USED for all production releases. Use PROACTIVELY to prepare releases and ensure smooth deployments.
task-commit-manager
Manages task completion and git commit workflows, ensuring proper documentation and version control practices for completed tasks.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.