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/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/release-auditor)<a href="https://agentmods.dev/agents/vmobifystudio/app-dev-team/release-auditor"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/release-auditor/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/vmobifystudio/app-dev-team/release-auditor"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/release-auditor.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.00057 | $0.01039 |
| Opus 5.5 | $0.00023 | $0.00416 |
| Sonnet 5.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 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 — 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.
- 1mo 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 2d ago), licensed MIT. It adds 57 tokens to every session and 1,039 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-31.
Other agents, from other repositories
integration-agent
Use when implementation and code review are complete — updates CHANGELOG, commits all changes, opens a PR, watches CI, merges when green, closes the linked issue, and prunes the local branch.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
release-engineer
Panel judge for the toolchain and the path to ship. Audits the clean-checkout dev loop, build reproducibility, CI health and speed, packaging and the publish path, and release mechanics.
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
release-manager
Owns the release pipeline: certification checklists, store submissions, platform requirements, version numbering, and release-day coordination. Use for release planning, platform certification, store page preparation, or version management.