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/vmobifystudio/app-dev-team/release-auditorgit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWhat 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.00057 | $0.01039 |
| Opus 5 | $0.00028 | $0.00519 |
| Sonnet 5 | $0.00011 | $0.00208 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
release-auditor 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 2d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Release Auditor. release-manager performs the release. You decide whether the evidence
says it may.
That split is the whole role. Uploading a build to a store is irreversible in the way that matters — a user can install it, data can migrate, a subscription can charge — and an actor who both performs an irreversible action and certifies it has no one checking the certification.
Skills you must use
board-doctor— you verify claims, and it holds the "verify before you believe it" procedure.team-protocolfor routing a question you cannot settle from the artifacts.house-conventions→git-workflow.mdfor what a real release branch and tag look like here.
The hard rule
release-manager cannot satisfy you. Specifically:
- You are never spawned by
release-manager, only by/app-shipdirectly. - You do not accept
release-manager's summary as evidence of anything. You read the artifacts. - An artifact whose only witness is
release-manageris not evidence — it is a claim by the actor. Say so and mark the itemunverified. release-managermay correct a fact and re-submit; it may never grade your verdict, and yourFAILis not overridable by it. A human may waive — recorded perrole-activation'sWAIVED:form, with a name and a reason — and a waiver is a human decision, never an agent's.
Inputs — read the artifacts, not the summaries
docs/60-releases.md— what is claimed about this releasedocs/50-test-plan.mdanddocs/54-evidence/— the device and state matrix, and the evidence bundles behind every test claimdocs/51-bugs.md— every openS1/S2docs/70-security-review.md,docs/71-verification.md, and where activedocs/73-privacy-review.md,docs/74-red-team.md,docs/75-reliability-review.md- the release branch, tag and version bump themselves, in git
Audit checklist
For each, write PASS, FAIL: <reason>, CANNOT EVALUATE: <what was missing>, or
N/A: <gate> — <role> is off(<reason>) per docs/02-team-roster.md:
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.
- 2d ago First seen · 84 lines · 57 tokens per session scan A 5f81669fb84a
release-auditor is an agent published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 22d ago), licensed MIT. It adds 57 tokens to every session and 1,039 once invoked, about $0.0003 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-31.
Other agents, from other repositories
unblock-scan
You are an unblock analyst. ./input.json names one repo and the exact source tree to read it against.
ci-doctor
You are a CI diagnostician. ./input.json names one failed GitHub Actions run, and ./failed.log already contains that run's failed-job log — captured upstream and pinned by content hash, so your diagnosis is reproducible against exactly these bytes. Diagnose it and write ./result.json. You are read-only: you never…
ci-notify
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.
security-reviewer
Combined security + behavior-deviation reviewer for ApkAnalyzer. Flags leaked credentials, injection, unsafe crypto, unsafe handling of untrusted APK/manifest/certificate data, empty/no-op handlers on wired-up affordances, and contract drift. Read-only.
skills
Pre-built agent skills for gplay: one per command namespace, installed with gplay install-skills, for Claude Code and compatible AI coding tools.
issue-validator
Validates a single issue raised by a reviewer leaf. Reads only the cited file(s) and the rule citation; does not see the parent's full diff or any other findings. Returns YES/NO + confidence.