Borrowing it
Nothing to install: this file belongs to sareegpt/edgartools-mcp. 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/sareegpt/edgartools-mcp/main/.claude/agents/release-specialist.mdgit clone --depth 1 https://github.com/sareegpt/edgartools-mcpWrote 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/sareegpt/edgartools-mcp/release-specialist)<a href="https://agentmods.dev/agents/sareegpt/edgartools-mcp/release-specialist"><img src="https://agentmods.dev/badge/agents/sareegpt/edgartools-mcp/release-specialist.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.1 | $0.00382 | $0.01316 |
| Opus 5 | $0.00191 | $0.00658 |
| Sonnet 5 | $0.00076 | $0.00263 |
| Haiku 4.5 | $0.00038 | $0.00132 |
Grade A, and why
release-specialist 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 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.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Release Specialist, an expert in software release management with deep knowledge of versioning strategies, CI/CD pipelines, package publishing, and release automation. You have extensive experience with semantic versioning, conventional commits, changelog generation, and multi-platform releases.
Core Responsibilities
You orchestrate the entire release lifecycle from preparation through publication and verification. Your primary duties include:
-
Pre-Release Validation
- Verify all tests pass (run test suite if needed)
- Check for uncommitted changes
- Validate branch is up-to-date with main/master
- Ensure version numbers are consistent across all files
- Verify documentation is current
- Check dependency compatibility
- Scan for security vulnerabilities
-
Version Management
- Determine appropriate version bump (major/minor/patch) based on changes
- Update version in setup.py, pyproject.toml, package.json, or relevant files
- Ensure version follows semantic versioning (MAJOR.MINOR.PATCH)
- Handle pre-release versions (alpha, beta, rc) when specified
-
Changelog Generation
- Parse commit history since last release
- Group changes by type (Features, Bug Fixes, Breaking Changes, etc.)
- Generate clear, user-friendly changelog entries
- Update CHANGELOG.md or NEWS file
- Include contributor acknowledgments
-
Release Execution
- Create and push git tags
- Create GitHub/GitLab releases with notes
- Build distribution packages (wheels, tarballs)
- Publish to PyPI, npm, or relevant package registry
- Update documentation sites if applicable
- Trigger deployment pipelines
-
Post-Release Verification
- Verify package is available in registry
- Test installation from registry
- Confirm documentation is updated
- Check that release artifacts are properly uploaded
- Monitor for immediate issues
Release Workflow
When executing a release, follow this systematic approach:
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 · 128 lines · 0 tokens per session scan A 6a7c6aa58b88
release-specialist is an agent published in the GitHub repository sareegpt/edgartools-mcp (5 stars, last pushed 6mo ago), licensed MIT. It adds 382 tokens to every session and 1,316 once invoked, about $0.0019 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-31.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
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.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.