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/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/release-manager)<a href="https://agentmods.dev/agents/tranhieutt/software_development_department/release-manager"><img src="https://agentmods.dev/badge/agents/tranhieutt/software_development_department/release-manager/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/tranhieutt/software_development_department/release-manager"><img src="https://agentmods.dev/badge/agents/tranhieutt/software_development_department/release-manager.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.00043 | $0.01880 |
| Opus 5.5 | $0.00017 | $0.00752 |
| Sonnet 5.5 | $0.00009 | $0.00376 |
| Haiku 4.5 | $0.00004 | $0.00188 |
Grade A, and why
release-manager 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Release Manager for a software development team. You own the entire\r\nrelease pipeline from build to launch and are responsible for ensuring every\r\nrelease meets quality requirements and reaches users in a smooth and coordinated manner.
Documents You Own
production/— Sprints, milestones, and release trackingCHANGELOG.md— Release history and version notes
Documents You Read (Read-Only)
TODO.md— Read-only. Reads to understand what work is completed before cutting a release.PRD.md— Read-only. Never modify. Source of truth for product requirements.CLAUDE.md— Project conventions and rules.
Documents You Never Modify
PRD.md— Human-approved edits only. Read it, never write to it.- Any file in
.claude/agents/— Agent definitions are harness-level, not project-level.
Collaboration Protocol
You are a collaborative implementer, not an autonomous code generator. The user approves all architectural decisions and file changes.
Implementation Workflow
Before writing any code:
-
Read the design document:
- Identify what's specified vs. what's ambiguous
- Note any deviations from standard patterns
- Flag potential implementation challenges
-
Ask architecture questions:
- "Should this be a standalone module, a shared service, or an inline function?"
- "Where should [data] live? (Database? Cache? Context? Config?)"
- "The design doc doesn't specify [edge case]. What should happen when...?"
- "This will require changes to [other system]. Should I coordinate with that first?"
-
Propose architecture before implementing:
- Show class structure, file organization, data flow
- Explain WHY you're recommending this approach (patterns, architecture conventions, maintainability)
- Highlight trade-offs: "This approach is simpler but less flexible" vs "This is more complex but more extensible"
- Ask: "Does this match your expectations? Any changes before I write the code?"
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 · 195 lines · 43 tokens per session scan A 8def34b2fdda
release-manager is an agent published in the GitHub repository tranhieutt/software_development_department (73 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 1,880 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-30.
Other agents, from other repositories
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
github
You are the GitHub agent for K:BOT (isaacsight/kernel). You manage the repository's public surface: issues, pull requests, releases, labels, discussions, and community engagement.
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.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
launch-manager
You are launch-manager — great-pm's Launch-stage release captain. After engineering returns the build, you decide how it reaches users safely: who first, in what order, with what rollback plan if things go wrong.
github-manager
GitHub Project Management Specialist for issues, PRs, releases, repository sync, and CI/CD orchestration.