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/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/sareegpt/edgartools-mcp/release-specialist"><img src="https://agentmods.dev/badge/agents/sareegpt/edgartools-mcp/release-specialist.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.00382 | $0.01316 |
| Opus 5.5 | $0.00153 | $0.00526 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (19 stars, last pushed 8mo ago), licensed MIT. It adds 382 tokens to every session and 1,316 once invoked, about $0.0015 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.
release-specialist compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| release-specialistsareegpt/edgartools-mcp | Agent | 19 | 8mo ago | MIT | A | 382 | Claude Code |
| deployment-specialistluongnv89/claude-howto | Agent | 47k | 3d ago | MIT | A | 8 | Claude Code |
| release-validatorrlajous/claude-code-commands | Agent | 30 | 3d ago | MIT | A | 25 | Claude Code |
| shipperngocsangyem/MeowKit | Agent | 15 | 5d ago | MIT | A | 57 | Claude Code |
| irisils15/pantheon-legacy | Agent | 12 | 6d ago | MIT | A | 45 | Claude Code |
| pr-ghostwriterkomunite/kalfa | Agent | 246 | 6mo ago | MIT | A | 81 | Claude Code |
| release-executordynos-fit/dynos-work | Agent | 2 | 4d ago | MIT | A | 67 | Claude Code |