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-org-submissiongit 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-org-submission)<a href="https://agentmods.dev/skills/mralaminahamed/wp-dev-skills/wp-org-submission"><img src="https://agentmods.dev/badge/skills/mralaminahamed/wp-dev-skills/wp-org-submission/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/mralaminahamed/wp-dev-skills/wp-org-submission"><img src="https://agentmods.dev/badge/skills/mralaminahamed/wp-dev-skills/wp-org-submission.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.00287 | $0.01861 |
| Opus 5 | $0.00143 | $0.00931 |
| Sonnet 5 | $0.00057 | $0.00372 |
| Haiku 4.5 | $0.00029 | $0.00186 |
Grade A, and why
wp-org-submission scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Invalid URLs in plugin header or readme.txt — verify with `curl -I` before submission. How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress.org Plugin Submission & SVN Deploy
Model note: SVN deploy steps and asset setup are mechanical (
haiku). Pre-submission rejection-pattern scan across a real codebase (17 patterns) requires code judgment — usesonnet. Responding to a human reviewer rejection also needssonnet.
Get a plugin into the WP.org directory and keep releasing to it. Two distinct phases — know which one applies:
- Phase 1 — Initial submission. Plugin not yet in the directory. One-time human review, then SVN access is granted.
- Phase 2 — SVN deploy. Plugin already approved. Ship a new version into the existing SVN repo.
wp-org-submission is about the directory/SVN side. Sync the version sources first with [[wp-plugin-release]] — this skill assumes the codebase already carries the target version.
When to use
- "Submit this plugin to WordPress.org", "publish to the .org directory", "add my plugin to wp.org".
- "Deploy the new version to SVN", "push the release to wp.org", "tag a release on plugins.svn".
- "Set up screenshots / banner / icon", "why aren't my assets showing".
- "Fix a WP.org rejection", "respond to plugin review email", "they flagged trialware / source code / external service".
- Pre-submission hygiene sweep using the 17-issue rejection catalog (real reviewer quotes).
Not for: "will this pass WP.org review?", "check guideline violations", "is my plugin GPL-compliant?" — use the official wp-plugin-directory-guidelines skill for authoritative 18-guideline compliance review. This skill owns the workflow (SVN, assets, rejections); that skill owns the rules.
Phase 1 — Initial submission
The review is done by humans and can take days to weeks. Submitting a clean plugin avoids round-trips.
- Slug availability — the directory slug is derived from the plugin name in the main file header. Pick a name not already taken at
https://wordpress.org/plugins/<slug>/(404 = free). Slug is permanent. - readme.txt valid — must parse in the official validator:
https://wordpress.org/plugins/developers/readme-validator/. Required header fields, validStable tag, GPL-compatibleLicense. Seereferences/submission-checklist.md. - Guidelines compliance — sanitize input, escape output, nonce-protect actions, prefix all globals, no obfuscation/minified-only code, no external loading of scripts, no tracking or calling home without explicit opt-in consent, GPL-compatible code + assets only. Full checklist in
references/submission-checklist.md. 17-issue catalog with exact reviewer quotes inreferences/review-issues-catalog.md. - Build a clean zip — source files (
src/,composer.json, build configs) must be included;.wordpress-org/andnode_modulesmust not. Full include/exclude lists in §4 ofreferences/submission-checklist.md. - Submit at
https://wordpress.org/plugins/developers/add/. The reviewer replies by email. Fix what they flag, reply briefly (context only, no change list), attach the updated zip. On approval, SVN access is granted athttps://plugins.svn.wordpress.org/<slug>/.
What ships with it
6 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.
- 11d ago First seen · 85 lines · 287 tokens per session scan A 55018da9095d
wp-org-submission is a skill published in the GitHub repository mralaminahamed/wp-dev-skills (27 stars, last pushed 1mo ago), licensed MIT. It adds 287 tokens to every session and 1,861 once invoked, about $0.0014 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
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.