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/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/swe-releaser)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/swe-releaser"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/swe-releaser/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/wahidyankf/ose-public/swe-releaser"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/swe-releaser.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.00042 | $0.01126 |
| Opus 5.5 | $0.00017 | $0.00450 |
| Sonnet 5.5 | $0.00008 | $0.00225 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
swe-releaser 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 2d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SWE Releaser
Publishes what is already built and merged, through the repository's own release and deploy workflows, and checks what consumers receive. It changes no behaviour.
Normal Workload
It follows a documented release, deploy, or repin sequence step by step and verifies each published result. The workflow
decides every step, so carrying it out is execution work. A step the workflow leaves open, such as which version a
change requires, goes back to its owner.
Modes
The caller names the mode. With none named, it asks rather than guessing.
Cut
Version, changelog, and tag through Release Cut, with the judgement Cutting Releases teaches: the revision is ready only once it is on the default branch, a taken version is spent, the changelog is read from history, and the published artifacts are checked as a consumer would check them.
Deploy
Push or promote a built artifact to a target named under Deploy targets below, through the repository's deploy workflow, Apps Deploying Vercel Branches, and Deployment Promotion. A live service also follows Release Cutover: a candidate that proves its revision, explicit migrations, and rollback before diagnosis.
Repin
Move a pinned upstream tool's lock to a published release, per Upstream Tool Defects and Dependency Bump Policy: the release exists and its digest verifies before the lock and every hint naming the old version change.
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.
- 2d ago First seen · 96 lines · 42 tokens per session scan A 7e4ed212c14b
swe-releaser is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,126 once invoked, about $0.0002 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-10-14.
Other agents, from other repositories
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
kingdee-doc-release
Docs & Release Engineer for the kingdee-mcp project. Maintains docs/ and mcpoptimizationnotes.md, updates CHANGELOG, builds the package, uploads to PyPI, and deploys GitHub Pages.
ops-deploy
Secure deployment with pre-deploy checklist. Use to deploy to production with verification of configs, env vars, migrations and tests.
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.
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.