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.
npx agentmods add commands/j-pster/psters_ai_workflow/release-plugingit 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/commands/j-pster/psters_ai_workflow/release-plugin)<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/release-plugin"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/release-plugin.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 | $0.00000 | $0.00116 |
| Opus 5 | $0.00000 | $0.00058 |
| Sonnet 5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
release-plugin 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 4d 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
Release Plugin Command
Use this command to publish a new plugin release.
Inputs
- Target version (example:
0.1.2)
Steps
- Run plugin submission review.
- Confirm
CHANGELOG.mdhas## [<version>]. - Confirm
.cursor-plugin/marketplace.jsonuses<version>. - Ensure GitHub CLI is authenticated:
gh auth status- if needed:
gh auth login
- Execute:
./scripts/release-plugin.sh <version>
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.
- 4d ago First seen · 19 lines · 0 tokens per session scan A 87afb6e453b4
release-plugin is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (290 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 116 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 commands, from other repositories
pr-submit
Create git commit and submit current branch with Graphite (squashes commits and rebases stack).
OPSX: Archive
Archive a completed change in the experimental workflow.
release-isparto
You are the Team Lead. The user has run /release-isparto to publish a new version.
OPSX: Archive
Archive a completed change in the experimental workflow.
release
Format, bump version, commit and push plugin release. Ship it.
OPSX: Archive
Archive a completed change in the experimental workflow.