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 rules/j-pster/psters_ai_workflow/plugin-maintainer-flowgit clone --depth 1 https://github.com/J-Pster/Psters_AI_WorkflowWhat 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.00166 | $0.00166 |
| Opus 5 | $0.00083 | $0.00083 |
| Sonnet 5 | $0.00033 | $0.00033 |
| Haiku 4.5 | $0.00017 | $0.00017 |
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 3d 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 Maintainer Flow
When changes affect this plugin repository:
- Before commit, run
/review-plugin-submission. - Fix all blocking findings from submission review.
- If release-impacting, keep versions synchronized:
CHANGELOG.mdnew section.cursor-plugin/marketplace.json->metadata.version
- Validate templates with:
node scripts/validate-template.mjs
- Commit only after checks pass.
For publishing a release:
- Use
./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.
- 3d ago First seen · 26 lines · 166 tokens per session scan A 8c001d62d6ec
plugin-maintainer-flow is a cursor rule published in the GitHub repository J-Pster/Psters_AI_Workflow (290 stars, last pushed 5mo ago), licensed MIT. It adds 166 tokens to every session, about $0.0008 per session on Opus 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.
Other cursor rules, from other repositories
versioning
Semantic versioning rules for tagging releases.
release-checklist
What to update with each code change or version release.
release
Cut a versioned release of harness-mini — bump VERSION, roll the CHANGELOG, tag, and publish a GitHub release. Use when shipping a new version. Wraps bin/harness.sh release; covers the human-judgment steps (semver choice, changelog curation) the script can't make.
release-management
CHANGELOG.md and README.md update requirements for every release of the tool.
release-policy
Release, versioning, and signing policy for setmac.
versioning
Repositório ia-config — ao mudar rule, command ou skill versionado, incrementar o VERSION do próprio arquivo.