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 skills add mralaminahamed/wp-dev-skills --skill wp-plugin-releasegit clone --depth 1 https://github.com/mralaminahamed/wp-dev-skillsWrote 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/mralaminahamed/wp-dev-skills/wp-plugin-release)<a href="https://agentmods.dev/skills/mralaminahamed/wp-dev-skills/wp-plugin-release"><img src="https://agentmods.dev/badge/skills/mralaminahamed/wp-dev-skills/wp-plugin-release.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.1 | $0.00276 | $0.01041 |
| Opus 5 | $0.00138 | $0.00521 |
| Sonnet 5 | $0.00055 | $0.00208 |
| Haiku 4.5 | $0.00028 | $0.00104 |
Grade A, and why
wp-plugin-release 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 8d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Plugin Release / Version Sync
Model note: Mechanical file edits — works well on
haiku. No reasoning across ambiguous code; all sources are explicit (header, constant, readme.txt, changelog).
Bump a WP plugin version coherently. Prevents the classic drift where the plugin header says one version, the readme.txt Stable tag another, and the .pot a third.
When to use
- "Release X.Y.Z", "bump the version", "update the changelog / readme.txt".
- After substantial work has landed under an unreleased version.
Not for: WP.org SVN deploy (trunk/tags/assets push) — use wp-org-submission. First-time plugin submission to the WP.org directory — use wp-org-submission.
First: determine the real current state
git tag # any release tags?
gh release list # any published releases?
grep -n "Version:" *.php # plugin header
grep -n "_VERSION'" *.php # version constant
grep -n "Stable tag" readme.txt
If header/constant/Stable-tag disagree, that drift IS the problem — pick the target version and sync all of them. Choose the bump by semver: new backward-compatible features → minor; fixes only → patch; breaking → major. Internal-only refactors (dir rename) don't force a major.
Sources to update (all, in lockstep)
- Plugin header
* Version: X.Y.Z(main plugin file). - Version constant
define( 'PLUGIN_VERSION', 'X.Y.Z' ). readme.txtStable tag: X.Y.Z— andTested up to/Requires PHPif they changed.readme.txtChangelog — add a= X.Y.Z =block listing what shipped (security, features, fixes), grouped.readme.txtUpgrade Notice — add= X.Y.Z =one-liner (why upgrade)..pot— regenerate soProject-Id-Versionmatches and new strings are captured:composer makepot # or: wp i18n make-pot . languages/<slug>.pot --exclude=...
Do NOT bump
- Schema / DB version (e.g.
LicenseModel::$db_version) — independent of plugin version. Only bump when the table actually changed, since it gates data migrations. - Historical changelog entries or point-in-time docs.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 62 lines · 276 tokens per session scan A c2ff21d05f63
wp-plugin-release is a skill published in the GitHub repository mralaminahamed/wp-dev-skills (27 stars, last pushed 1mo ago), licensed MIT. It adds 276 tokens to every session and 1,041 once invoked, about $0.0014 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 skills, from other repositories
release
Cut a new release: group Conventional Commits since the last tag, append a CHANGELOG section, create a release commit, and add an annotated git tag. TRIGGER when the user says "cut a release", "tag a release", "release v1.2.0", "ship version 1.2.0", "create a release for 1.2.0", "bump the version to 1.2.0", "make a…
hotfix
Set up the branch topology for a patch release against a previously tagged version: ensures release/ . exists from the source tag, then creates hotfix/ off it. TRIGGER when the user says "hotfix v1.0.0", "patch the release", "I need to fix something in the v2 line", "create a hotfix branch", "/nyann:hotfix". Match…
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
version-release
Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.