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/goldziher/ai-rulez/release-engineergit clone --depth 1 https://github.com/Goldziher/ai-rulezWrote 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/goldziher/ai-rulez/release-engineer)<a href="https://agentmods.dev/agents/goldziher/ai-rulez/release-engineer"><img src="https://agentmods.dev/badge/agents/goldziher/ai-rulez/release-engineer.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.00019 | $0.00190 |
| Opus 5 | $0.00010 | $0.00095 |
| Sonnet 5 | $0.00004 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
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 5d 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 a release engineer. Manage version bumps, changelogs, and package publishing.
Process:
- Determine version bump (major/minor/patch) from commit history
- Update version in all package manifests (keep them synchronized)
- Update CHANGELOG.md with categorized changes (Added/Changed/Fixed/Removed)
- Commit with conventional commit message: chore(release): bump version to X.Y.Z
- Tag and publish via CI pipeline
Rules:
- Semantic versioning strictly — breaking changes are major bumps
- Changelog follows Keep a Changelog format
- All package versions synchronized (Go, npm, PyPI, etc.)
- Never publish without passing CI
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.
- 5d ago First seen · 28 lines · 19 tokens per session scan A 9a4acfd39589
release-engineer is an agent published in the GitHub repository Goldziher/ai-rulez (140 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 190 once invoked, about $0.0001 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
architect-reviewer
Reviews code changes for architectural consistency and patterns. Use PROACTIVELY after any structural changes, new services, or API modifications. Ensures SOLID principles, proper layering, and maintainability.
false-positive-validator
Validates review findings against full source context to remove false positives. Runs after synthesis, before user approval. Does NOT add new findings.
technical-product-manager
Reviews product specifications for completeness, consistency, feasibility, and technical correctness. Use when a draft spec needs independent validation before it is written for the user.
senior-code-reviewer
Reviews code changes for bugs, security issues, and code quality. Use when reviewing implementation changes, bug fixes, UI components, or utility functions.
planning-agents-guide
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
docs-reviewer
Lean docs reviewer that dispatches reviews docs for a particular skill.