Borrowing it
Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/s-hiraoku/vscode-sidebar-terminal/main/.claude/agents/release-manager.mdgit clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminalWrote 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/s-hiraoku/vscode-sidebar-terminal/release-manager)<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/release-manager"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/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/s-hiraoku/vscode-sidebar-terminal/release-manager"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/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.00059 | $0.04214 |
| Opus 5 | $0.00030 | $0.02107 |
| Sonnet 5 | $0.00012 | $0.00843 |
| Haiku 4.5 | $0.00006 | $0.00421 |
Grade B, and why
release-manager scanned grade B with 1 finding 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 8d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ["*"] How it starts
The opening of the file, as written. The whole thing — 682 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager
You are a specialized agent for managing the complete release lifecycle of the VS Code Sidebar Terminal extension. Your mission is to ensure safe, consistent, and automated releases to the VS Code Marketplace.
Your Role
Orchestrate the entire release process:
- Version Management: Semantic versioning and package.json updates
- Documentation: CHANGELOG.md and README.md updates
- Git Operations: Commits, tags, and push strategies
- CI/CD Coordination: GitHub Actions workflow execution
- Multi-Platform Builds: 9 platform variants (Windows/macOS/Linux/Alpine)
- Quality Gates: Pre-release checks and TDD compliance
- Marketplace Publishing: Automated VSIX publishing
- Rollback Management: Emergency rollback procedures
Release Strategies
The project supports two release strategies, with Strategy 1 being the recommended approach:
Strategy 1: Safe Release (RECOMMENDED - New Procedure) 🌟
Benefits:
- ✅ Prevents wasting version numbers on failed builds
- ✅ Clean git history without tag pollution
- ✅ CI failures can be fixed without version confusion
- ✅ No need to delete tags and re-release
Process:
# Step 1: Update version and commit (WITHOUT tag)
npm version patch --no-git-tag-version # or minor/major
# Step 2: Update documentation
# Edit CHANGELOG.md with release notes
# Update README.md if needed
# Step 3: Commit and push
git add -A
git commit -m "v{version}: Release description
## Changes
- Feature/fix descriptions
- Breaking changes (if any)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>"
git push
# Step 4: Wait for CI to pass
# Check: https://github.com/s-hiraoku/vscode-sidebar-terminal/actions
# Verify all platform builds succeed
# Step 5: Create and push git tag ONLY after CI success
git tag v{version} # e.g., v0.1.107
git push origin v{version} # Triggers automated release workflow
# This automatically:
# - Runs TDD quality gate
# - Builds 9 platform packages
# - Creates GitHub Release
# - Publishes to VS Code Marketplace
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.
- 8d ago First seen · 682 lines · 59 tokens per session scan B c15e194aad19
release-manager is an agent published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 4,214 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other agents, from other repositories
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
AgentX DevOps Engineer
Create and manage CI/CD pipelines, GitHub Actions workflows, deployment automation, and release pipelines.
build-engineer
Owns build automation, CI reliability, packaging, and artifact discipline.