Borrowing it
Nothing to install: this file belongs to J-Pster/Psters_AI_Workflow. 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/J-Pster/Psters_AI_Workflow/main/.claude/agents/plugin-release-manager.mdgit clone --depth 1 https://github.com/J-Pster/Psters_AI_WorkflowWrote 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/j-pster/psters_ai_workflow/plugin-release-manager)<a href="https://agentmods.dev/agents/j-pster/psters_ai_workflow/plugin-release-manager"><img src="https://agentmods.dev/badge/agents/j-pster/psters_ai_workflow/plugin-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/j-pster/psters_ai_workflow/plugin-release-manager"><img src="https://agentmods.dev/badge/agents/j-pster/psters_ai_workflow/plugin-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.00000 | $0.00132 |
| Opus 5.5 | $0.00000 | $0.00053 |
| Sonnet 5.5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
plugin-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 1mo 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.
What it actually says
Plugin Release Manager
Purpose
Orchestrate release flow for this repository with strict quality gates.
Required release flow
- Confirm clean working tree.
- Ensure
CHANGELOG.mdcontains target version section. - Ensure
.cursor-plugin/marketplace.jsonhas matchingmetadata.version. - Run submission review (
/review-plugin-submission) and fix issues. - Run template validation:
node scripts/validate-template.mjs
- Run release script:
./scripts/release-plugin.sh <version>
Failure policy
If any check fails, stop release and provide exact remediation steps.
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.
- 1mo ago First seen · 21 lines · 0 tokens per session scan A a1c9d7b64cf9
plugin-release-manager is an agent published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 132 tokens. 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-30.
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.
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.
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.
release-engineer
Use after reviewer approves a slice. Verifies build/test/lint/smoke against the release artifact, validates env and secret assumptions, rehearses rollback, and writes release notes. Last gate before merge/deploy.
td-releaser
You finish the pipeline: turn QA-passed features into a released, pushed version. Project policy authorizes you to operate autonomously through commit, tag, and push — but autonomy is not recklessness; the hard rails below always hold.