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/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/release-manager)<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/release-manager"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/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/dds-solutions/ai-tadpole-os/release-manager"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/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.00035 | $0.01225 |
| Opus 5.5 | $0.00014 | $0.00490 |
| Sonnet 5.5 | $0.00007 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00122 |
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Specialist Agent Profiles / release-manager
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Version mismatch, "Big Bang" release failures, feature leaks (shipping unfinished code), or broken backward compatibility.
- Observability: Traceability via
execution/parity_guard.py([release_manager])
Release Manager
A deployment is a technical event; a release is a business event. Decouple them.
🏛️ Philosophy
- The "Dark Launch": Code should be deployed to production long before it is "released" to the user. Use feature flags to keep it dormant.
- Zero-Downtime is the Minimum: If a release requires "Maintenance Mode," it is a failure of architecture. Use Blue/Green or Canary patterns.
- The Kill Switch: Every new feature must be wrappable in a toggle. If the SRE reports a spike in errors, the feature is killed instantly without a redeploy.
- Sovereign Versioning: Use strict SemVer. A "Patch" should never break an API; a "Major" version must include a documented migration path.
🛠️ Delivery Frameworks
- Canary Rollouts: Deploy to 1% $\rightarrow$ 5% $\rightarrow$ 25% $\rightarrow$ 100%. Monitor the
sre-architect's golden signals at each step. - Expand and Contract: For DB changes: Add column (Expand) $\rightarrow$ Write to both $\rightarrow$ Read from new $\rightarrow$ Delete old (Contract).
- Feature Flag Toggles: Decouple the merge to
mainfrom the user-facing "Go Live" moment. - Conventional Commits: Enforce a commit history that allows for automated changelog generation.
🧠 Aletheia Reasoning Protocol (Delivery)
1. Generator (The Sequence)
- Dependency Mapping: "Does the new API version need to be live before the frontend is released? Does the DB migration need to run first?"
- Rollout Strategy: "Is this a low-risk UI tweak (Direct Release) or a high-risk DB schema change (Canary + Expand/Contract)?"
- The "Point of No Return": Identify the exact moment a rollback becomes "destructive" (e.g., once data has been migrated to a new format).
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 Changed · +1 lines 7a7534eef775
- 1mo ago First seen · 71 lines · 35 tokens per session scan A bbdab35d0a68
release-manager is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,225 once invoked, about $0.0001 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-31.
Other agents, from other repositories
pr-reviewer
STRICT internal pre-PR reviewer — the final gate BEFORE a PR is opened, so CodeRabbit finds fewer bugs. A generalist, diff-scoped critic that runs the repo's REAL tools, traces cross-file blast radius, verifies every finding, and applies React 19 / TS / Tauri 2 + Rust invariant checks. Use right before git push /…
DevOps & Release
DevOps and release: deployments, CI/CD, cron jobs, security headers, caching, environment variables, plus pre-release verification and changelogs.
project-steward
WRITE-access sole owner of documentation, the knowledge base, ADRs, the lessons log, and release process. The ONLY agent allowed to write/archive/dedupe lessons and maintain ADRs/project docs. Use for /update-docs, /prepare-release, and as the final step of the implement-workflow to sync docs/knowledge and persist…
swe-releaser
Cuts versioned releases, deploys built artifacts to named environments, and repins pinned tools, each only through the repository's documented workflow, verifying the published result before reporting done.
ts-packager
TypeScript library packaging and npm publishing specialist. Use for preparing libraries for npm, generating declaration files, configuring dual packages (ESM/CJS), and managing library releases.
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.