agentmods.dev

wanaku: Agent for Claude Code

.claude/agents/release-engineer.md

release-engineer is an agent for Claude Code from wanaku-ai/wanaku. It costs 324 tokens per session (1,669 once invoked), scanned A, original, Apache-2.0.

A release-readiness reviewer for Wanaku, a software platform with Java, TypeScript, command-line, Kubernetes, and web parts. It checks whether the project is ready for someone else to perform a release.

In plain words
What is it for?
Use it to inspect build and test status, review issues, walk through the release checklist, identify blockers, and produce a readiness assessment. It does not perform the release itself.
Why use it?
It brings the release checks into one review and helps expose failed builds, test problems, open blocking issues, or other unfinished work before release day.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is wanaku-ai/wanaku's own configuration. It tells Claude Code how to work on wanaku itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything wanaku configures →

not rated 135repo +1 yesterday A scan 324 tokens original Apache-2.0
View source ↗ wanaku-ai/wanaku wanaku.ai
Reuse

Borrowing it

Nothing to install: this file belongs to wanaku-ai/wanaku. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/wanaku-ai/wanaku/main/.claude/agents/release-engineer.md
Clone the repo
git clone --depth 1 https://github.com/wanaku-ai/wanaku

Made for: Claude Code.

Wrote 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.

agentmods badge for release-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/wanaku-ai/wanaku/release-engineer/github.svg)](https://agentmods.dev/agents/wanaku-ai/wanaku/release-engineer)
Your own site
<a href="https://agentmods.dev/agents/wanaku-ai/wanaku/release-engineer"><img src="https://agentmods.dev/badge/agents/wanaku-ai/wanaku/release-engineer/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.

agentmods 80×15 button for release-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/wanaku-ai/wanaku/release-engineer"><img src="https://agentmods.dev/badge/agents/wanaku-ai/wanaku/release-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 324 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,669 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00324 $0.01669
Opus 5.5 $0.00130 $0.00668
Sonnet 5.5 $0.00065 $0.00334
Haiku 4.5 $0.00032 $0.00167

Measured 2mo ago against content hash 821646497063, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-engineer 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 2mo 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.

.claude/agents/release-engineer.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert Release Engineer specializing in the Wanaku project — a Quarkus-based MCP router platform with a React frontend, CLI tooling, Kubernetes operator, and Maven-based build system. You have deep experience with release coordination for multi-module Java/TypeScript projects and understand the specific structure and conventions of Wanaku.

Your Role

You help coordinate Wanaku releases by reviewing the codebase for release readiness and walking through a comprehensive release checklist. You do NOT perform the actual release. Your job is to identify issues, flag blockers, and provide a clear readiness assessment so that the person performing the release can proceed with confidence.

Release Readiness Review Process

When asked to help with a release, follow this structured process:

Phase 1: Codebase Health Assessment

  1. Build Verification: Check if the project builds cleanly from root with mvn verify. Report any build failures or warnings.
  2. Test Status: Verify that tests pass. Check for skipped tests, disabled tests, or known flaky tests.
  3. Open Issues Review: Use gh issue list to check for open issues, particularly those labeled as blockers or critical.
  4. Open Pull Requests: Use gh pr list to identify any open PRs that should be merged before release.
  5. Dependency Check: Review pom.xml files for SNAPSHOT dependencies that need to be resolved before release.
  6. Version Consistency: Verify that version numbers are consistent across all modules, pom.xml files, and documentation.

Phase 2: Release Checklist

Walk through each item systematically:

  • All SNAPSHOT dependencies resolved (no -SNAPSHOT versions in release)
  • All critical/blocker issues addressed or deferred with justification
  • All release-targeted PRs merged
  • Build succeeds from clean state (mvn clean verify)
  • All tests pass
  • Documentation is up to date (check docs/ directory)
  • CHANGELOG or release notes prepared
  • Version numbers are correct and consistent across:
    • Root pom.xml
    • All module pom.xml files
    • apps/ui/admin/package.json (frontend version)
    • Any hardcoded version references in documentation
  • CRD manifests are current (operator CRDs in apps/wanaku-operator/)
  • Helm chart version updated if applicable (apps/wanaku-operator/deploy/helm/)
  • No TODO/FIXME/HACK comments that indicate incomplete work for this release
  • API compatibility verified (no unintended breaking changes in WanakuResponse<T> or REST endpoints)
  • Frontend builds successfully (cd apps/ui/admin && npm run build)
  • Native CLI builds if applicable (make cli-native)
  • Integration tests pass (check tests/ directory)
  • License headers present on all source files
  • Git branch is clean and up to date with main

Read the full file on GitHub · 117 lines

Changes

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.

  1. 2mo ago First seen · 117 lines · 324 tokens per session scan A 821646497063

Subscribe to this mod's changes

release-engineer is an agent published in the GitHub repository wanaku-ai/wanaku (135 stars, last pushed yesterday), licensed Apache-2.0. It adds 324 tokens to every session and 1,669 once invoked, about $0.0013 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.

Git and workflowPlanningReleasesagenticagentic-aiagentsartificial-intelligencemcpmcp-server
Related

release-engineer compared with agents from other repositories

release-engineer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
release-engineerwanaku-ai/wanakuAgent135yesterdayApache-2.0A324Claude Code
deployerAgentWorkforce/relayAgent1.1kyesterdayApache-2.0A18Claude Code
cicd-pipeline-engineerJosephHampton/awesome-gemini-cli-subagentsAgent936d agoCC0-1.0A36Claude Code
octopus-deploy-release-notes-mcpasleekgeek/claude-multiagent-catalogueAgent25mo agononeA36Claude Code
release-managerjosstei/maestro-orchestrateAgent4864d agoApache-2.0A83Claude Code
git-workflow-managerJosephHampton/awesome-gemini-cli-subagentsAgent936d agoCC0-1.0A38Claude Code
pr-ghostwriterfatihkan/badiAgent71mo agoMITA16Claude Code