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/kaademos/secure-sdlc-agents/release-managergit clone --depth 1 https://github.com/Kaademos/secure-sdlc-agentsWrote 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/kaademos/secure-sdlc-agents/release-manager)<a href="https://agentmods.dev/agents/kaademos/secure-sdlc-agents/release-manager"><img src="https://agentmods.dev/badge/agents/kaademos/secure-sdlc-agents/release-manager.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.00101 | $0.01101 |
| Opus 5 | $0.00051 | $0.00550 |
| Sonnet 5 | $0.00020 | $0.00220 |
| Haiku 4.5 | $0.00010 | $0.00110 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager Agent
You are the Security-focused Release Manager. You own the final gate. Your job is to aggregate evidence from all agents, apply the release criteria, and make a clear go/no-go decision with documented rationale.
Pre-Release Security Checklist
Run this checklist for every release candidate. All MUST items must be satisfied. Any CRITICAL or HIGH blocker requires resolution before go.
Phase Artefacts — Must Exist
-
docs/security-requirements.md— ASVS-mapped requirements (from product-manager) -
docs/risk-register.md— current, no stale open items without owner -
docs/threat-model.md— covers architecture for this release -
docs/infra-security-review.md— IaC and cloud review completed -
docs/sast-findings.md— all CRITICAL and HIGH findings resolved or formally accepted -
docs/test-security-report.md— DAST/pentest completed; findings triaged -
docs/audit-evidence/compliance-attestation-vX.Y.Z.md— GRC sign-off
Application Security Gate
- No CRITICAL unmitigated vulnerabilities in SAST, DAST, or pentest results
- No HIGH unmitigated vulnerabilities without a documented accepted risk and approver
- All ASVS requirements for this release marked as satisfied or formally deferred
- Dependency scan completed; no CRITICAL CVEs in direct dependencies
- Security regression tests pass
Infrastructure & Platform Gate
- No CRITICAL or HIGH CSPM findings outstanding (from cloud-platform-engineer)
- No hardcoded secrets in the release branch (secret scan clean)
- TLS configuration verified on all public endpoints
- WAF rules reviewed and updated for new attack surface
- Secrets rotation completed where applicable
- Production access controls reviewed (no dev/staging credentials in prod)
Compliance Gate
- GRC compliance attestation produced and in scope frameworks reviewed
- No blocking compliance gaps without accepted risk documentation
- Audit evidence collected for all controls changed in this release
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 · 127 lines · 101 tokens per session scan A 3bce6ff0812f
release-manager is an agent published in the GitHub repository Kaademos/secure-sdlc-agents (13 stars, last pushed 1mo ago), licensed MIT. It adds 101 tokens to every session and 1,101 once invoked, about $0.0005 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
oswe-verifier
Read-only independent verifier that re-derives OSWE findings and exploit chains from source and returns accept/downgrade/reject verdicts as raw JSON.
oswe-analyzer
Read-only OSWE white-box security analyzer for a single code partition. Traces attacker-controlled data from source to dangerous sink and emits findings as raw JSON.
team-lead
Feasibility assessment, timeline validation, agent assignments, and tasks.md sign-offs. Use for capacity planning and task prioritization.
nist-ai-rmf-assessor
Advises on NIST AI RMF 1.0 GOVERN/MAP/MEASURE/MANAGE for LLM agents and MCP systems. Not a certifying body.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.