Borrowing it
Nothing to install: this file belongs to reorder-js/reorder. 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/reorder-js/reorder/main/.agents/skills/release-plugin/SKILL.mdgit clone --depth 1 https://github.com/reorder-js/reorderWrote 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/skills/reorder-js/reorder/release-plugin)<a href="https://agentmods.dev/skills/reorder-js/reorder/release-plugin"><img src="https://agentmods.dev/badge/skills/reorder-js/reorder/release-plugin/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/skills/reorder-js/reorder/release-plugin"><img src="https://agentmods.dev/badge/skills/reorder-js/reorder/release-plugin.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.01026 |
| Opus 5.5 | $0.00000 | $0.00410 |
| Sonnet 5.5 | $0.00000 | $0.00205 |
| Haiku 4.5 | $0.00000 | $0.00103 |
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 2mo 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-plugin
This skill automates the process of releasing the Medusa plugin, ensuring that NPM releases and GitHub releases are perfectly synced. It handles testing, building, version bumping, changelog generation, tagging, and creating the GitHub release, leaving only the final NPM publish step for the user to handle interactively.
When to use
Use this skill when the user asks to release a new version of the plugin, publish to NPM, create a GitHub release, or complains about a mismatch between NPM packages and the GitHub repository state.
Rules & Philosophy
- Always keep GitHub and NPM in sync. A published NPM package should always have a corresponding Git tag and GitHub release. This ensures a single source of truth for changelogs, easier debugging, and provenance tracking.
- Automate everything possible, but respect auth. Do all the heavy lifting (changelog, git, bumping, gh release) but leave
npm publishto the user to prevent 2FA/auth hangs in the agent context. - Validate before release. Never release a broken build.
Steps to execute
1. Pre-flight Checks
- Check if the working directory is clean (
git status --porcelain). If not, tell the user to commit or stash changes before releasing. - Check if
ghCLI is installed (gh --version). If not, advise the user to install it (brew install gh) and authenticate (gh auth login) before proceeding.
2. Validation & Build
- Verify in
package.jsonthat the package has the correct keywords for the Medusa v2 ecosystem (e.g.,medusa-v2,medusa-plugin-integration) and that theexportsobject points to the built files in the./.medusa/server/src/...directory (a Medusa v2 requirement). - Run all test suites automatically before building to ensure correctness:
yarn test:integration:modulesyarn test:integration:httpyarn test:e2e(Note: Ensure the local Medusa backend is running or started as required by E2E tests).
- Run
yarn build(which internally runsmedusa plugin:build) to compile the plugin code into the.medusa/serverdirectory.
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.
- 2mo ago First seen · 57 lines · 0 tokens per session scan A 135c785502e8
release-plugin is a skill published in the GitHub repository reorder-js/reorder (59 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,026 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-09-07.
release-plugin compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| release-pluginreorder-js/reorder | Skill | 59 | 12d ago | MIT | A | 0 | Claude Code, Codex |
| draft-release-notesprisma/orm | Skill | 48k | yesterday | Apache-2.0 | A | 174 | Claude Code, Codex |
| publish-npm-versionprisma/orm | Skill | 48k | yesterday | Apache-2.0 | A | 182 | Claude Code, Codex |
| releasesonichi/sutando | Skill | 404 | yesterday | MIT | A | 68 | Codex |
| ship-workflowMathews-Tom/armory | Skill | 340 | 5d ago | MIT | A | 158 | Claude Code |
| changelog-composerMathews-Tom/armory | Skill | 340 | 5d ago | MIT | A | 67 | Claude Code |
| repo-sentinelMathews-Tom/armory | Skill | 340 | 5d ago | MIT | A | 65 | Claude Code |