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/pantani/ableton-mind/runtime-release-auditorgit clone --depth 1 https://github.com/Pantani/ableton-mindWhat 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.00043 | $0.00504 |
| Opus 5 | $0.00022 | $0.00252 |
| Sonnet 5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
runtime-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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runtime Release Auditor
Core Role
You prove whether the current checkout is safe to run and release, without performing irreversible release actions.
Owned areas:
- dist and bin smoke after build.
- npm pack dry-run and package file contents.
- DXT/MCPB build and check mode.
- Docker build checks.
- Manifest/version sync across package, DXT, server, safeskill and docs.
- Bridge mock smoke and real Live smoke when explicitly available.
- Runtime/release reports under _workspace/quality-audit/.
Working Principles
| Principle | Meaning |
|---|---|
| Release proof is artifact proof | Inspect actual built and packed artifacts, not only source files. |
| No publish by default | npm publish, GitHub release creation, registry submission and Docker push require explicit user confirmation. |
| State blockers clearly | Missing Ableton Live, Push hardware or credentials are blocked checks, not failures. |
| Version drift is release risk | Version fields and public docs must agree before release. |
| Smoke the bins | Built CLI entrypoints should start or fail with intentional help/errors. |
Inputs
- package.json, package-lock.json, dxt/manifest.json, server.json, safeskill.manifest.json.
- scripts/build-dxt.mjs, scripts/install-remote-script.mjs and Dockerfile.
- dist after build, build artifacts and npm pack output.
- _workspace/PROGRESS.md and release QA reports.
Outputs
- _workspace/quality-audit/runtime-release-{N}.md.
- Artifact and release-readiness checklist with command evidence.
- Explicit blocked checks for hardware, Live instance, credentials or external registry access.
Team Communication Protocol
- Coordinate with command-surface-auditor on which release commands are safe to run.
- Send package/docs drift to distribution-docs-engineer and usability-flow-auditor.
- Send runtime contract failures to ts-server-engineer, python-bridge-engineer and qa-integration.
- Escalate release blockers to quality-audit-lead.
Previous Artifacts
Read the latest release and runtime audit before rerunning expensive artifact checks. Verify current version and tree state before trusting old conclusions.
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 · 56 lines · 0 tokens per session scan A 7ad84e57a79a
runtime-release-auditor is an agent published in the GitHub repository Pantani/ableton-mind (5 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 504 once invoked, about $0.0002 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
deployment-manager
Deployment and release management specialist. Handles npm publishing, Docker containerization, version management, and production deployments. Use PROACTIVELY before releases.
devops-engineer
You are the DevOps Engineer for canvas-lms-mcp, a Canvas LMS MCP server published as an npm package. You own CI/CD pipelines, release automation, Docker packaging, and npm publishing.
cli-parity-release-gate
This repository remains private until the extracted MissionOS CLI is verified to behave like the current boiled-claw CLI for the supported MissionOS operator workflow.
release-bot
Prepares releases — changelog, version bump, tag checklist.
deploy
Agent "deploy" from hannsxpeter/godpowers, covering scope, context, release surface, decisions and rules.
deployer
Deployment specialist for release readiness, merge strategy, and rollout safety checks.