plugin-maintainer-flow

plugin-maintainer-flow is a cursor rule for Cursor from J-Pster/Psters_AI_Workflow. It costs 166 tokens per session, scanned A, original, MIT.

A set of rules for developing and releasing this plugin repository. It defines checks to run before commits and steps for preparing a release.

In plain words
What is it for?
Use it when reviewing plugin changes, validating templates, keeping the changelog and marketplace version aligned, or releasing a new plugin version.
Why use it?
It provides a repeatable maintenance process and helps catch template problems before changes are committed or published.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when reviewing plugin changes, validating templates, keeping the changelog and marketplace version aligned, or releasing a new plugin version.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/j-pster/psters_ai_workflow/plugin-maintainer-flow
Install

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.

Clone the repo
git clone --depth 1 https://github.com/J-Pster/Psters_AI_Workflow

Made for: Cursor.

Wrote 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.

agentmods badge for plugin-maintainer-flow

README.md
[![agentmods](https://agentmods.dev/badge/rules/j-pster/psters_ai_workflow/plugin-maintainer-flow/github.svg)](https://agentmods.dev/rules/j-pster/psters_ai_workflow/plugin-maintainer-flow)
Your own site
<a href="https://agentmods.dev/rules/j-pster/psters_ai_workflow/plugin-maintainer-flow"><img src="https://agentmods.dev/badge/rules/j-pster/psters_ai_workflow/plugin-maintainer-flow/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.

agentmods 80×15 button for plugin-maintainer-flow

Your own site · 80×15
<a href="https://agentmods.dev/rules/j-pster/psters_ai_workflow/plugin-maintainer-flow"><img src="https://agentmods.dev/badge/rules/j-pster/psters_ai_workflow/plugin-maintainer-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 166 This file is loaded in full into every session.
When invoked 166 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00166 $0.00166
Opus 5.5 $0.00066 $0.00066
Sonnet 5.5 $0.00033 $0.00033
Haiku 4.5 $0.00017 $0.00017

Measured 1mo ago against content hash 8c001d62d6ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plugin-maintainer-flow 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.

.cursor/rules/plugin-maintainer-flow.mdc · 26 lines

What it actually says

Plugin Maintainer Flow

When changes affect this plugin repository:

  1. Before commit, run /review-plugin-submission.
  2. Fix all blocking findings from submission review.
  3. If release-impacting, keep versions synchronized:
    • CHANGELOG.md new section
    • .cursor-plugin/marketplace.json -> metadata.version
  4. Validate templates with:
    • node scripts/validate-template.mjs
  5. Commit only after checks pass.

For publishing a release:

  • Use ./scripts/release-plugin.sh <version>.
Changes

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.

  1. 1mo ago First seen · 26 lines · 166 tokens per session scan A 8c001d62d6ec

Subscribe to this mod's changes

plugin-maintainer-flow is a cursor rule published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 7mo ago), licensed MIT. It adds 166 tokens to every session, about $0.0007 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-30.