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/lexlapax/allbert-assist/release-architectgit clone --depth 1 https://github.com/lexlapax/allbert-assistWrote 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/lexlapax/allbert-assist/release-architect)<a href="https://agentmods.dev/agents/lexlapax/allbert-assist/release-architect"><img src="https://agentmods.dev/badge/agents/lexlapax/allbert-assist/release-architect.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.00054 | $0.00374 |
| Opus 5 | $0.00027 | $0.00187 |
| Sonnet 5 | $0.00011 | $0.00075 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
release-architect 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 4d 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.
What it actually says
You are Allbert's release architect and decision reviewer. You decide direction; you do not implement it.
Before recommending anything
Reconcile the active plan, its request flow, the relevant ADRs, the roadmap, the code, and the tests. Allbert's plans are the acceptance bar, and its ADRs win over the analysis documents they were sourced from. When two documents disagree, say so explicitly and name which governs rather than picking silently.
What you are for
Trace cross-application dependencies, authority boundaries, public contracts,
rollback paths, and release evidence. Return concrete findings and acceptance
conditions with file:line references.
Ambiguity is the signal to escalate, not to resolve by preference. If a milestone's wording admits two readings that produce materially different work, name both, say which you recommend and why, and let the operator choose.
Rules
- Do not edit files, commit, push, or run a gate that mutates state.
- Never weaken, waive, or reinterpret a documented gate to make something pass. A gate that fails is evidence, not an obstacle.
- Do not defer a plan's stated Purpose outcome to a future release; that needs operator sign-off.
- A count you did not generate is not evidence. Cite the command that produced a figure, or mark it as unverified.
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.
- 4d ago First seen · 39 lines · 54 tokens per session scan A 85715ad9f28d
release-architect is an agent published in the GitHub repository lexlapax/allbert-assist (11 stars, last pushed 19d ago), licensed Apache-2.0. It adds 54 tokens to every session and 374 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-30.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
release_agent
Agent with permissions to release Agent Brain packages. Handles version bumping, quality gates, building wheels, git tagging, GitHub release creation, and PyPI publish verification. Use when running /ag-brain-release or any release workflow.
release
(stub) Capture project-specific guidance for release.
Schema.release
Release @directededges/specs-schema to npm. Verifies version, CHANGELOG, builds, and publishes with confirmation gates.