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 commands/automattic/pressship/publishgit clone --depth 1 https://github.com/Automattic/pressshipWrote 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/commands/automattic/pressship/publish)<a href="https://agentmods.dev/commands/automattic/pressship/publish"><img src="https://agentmods.dev/badge/commands/automattic/pressship/publish.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 | $0.00000 | $0.00486 |
| Opus 5 | $0.00000 | $0.00243 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
publish 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 5d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish
pressship publish ./my-plugin
publish is the modernized happy path for WordPress.org plugins. It discovers the plugin and chooses the best publishing flow:
- use
releasewhen running inside a WordPress.org SVN checkout frompressship get; - use
submitwhen a matching WordPress.org review submission is pending or reuploadable; - use
releasewhen the plugin has an approved WordPress.org SVN repository and no pending review submission is found; - ask whether to submit or release when Pressship cannot confidently choose.
Options
pressship publish ./my-plugin --dry-run
pressship publish ./my-plugin --submit
pressship publish ./my-plugin --release --username WpOrgUser
pressship publish ./my-plugin --no-verify
pressship publish ./my-plugin --skip-plugin-check
pressship publish ./my-plugin --skip-readme-validator
pressship publish ./my-plugin --wp-path /path/to/wordpress
pressship publish ./my-plugin --ignore "assets/**/*.mp4"
pressship publish ./my-plugin --yes
pressship publish ./my-plugin --release --no-install-svn
Use --submit for review upload and --release for approved-plugin SVN release when you want to force the route.
Before uploading or committing an SVN release, publish verifies the plugin with readme validation and Plugin Check. Use --no-verify only when you intentionally want to bypass both checks.
From an SVN checkout root, Pressship treats trunk/ as the plugin directory:
pressship get my-plugin ./my-plugin
cd ./my-plugin
pressship version patch
pressship publish
For SVN releases, Pressship can infer the username from the saved WordPress.org login. On the first real release commit, it will ask for a generated WordPress.org SVN password and save it locally for later releases.
When the selected release version already exists in SVN as tags/<version>, Pressship stops with a “No version change detected” message. Bump the plugin version before publishing again.
If svn is missing during a release, Pressship can detect your operating system and ask before installing Subversion. Use --no-install-svn to skip that helper.
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.
- 5d ago First seen · 51 lines · 0 tokens per session scan A 725ede55fe2f
publish is a command published in the GitHub repository Automattic/pressship (51 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 486 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-08-30.
Other commands, from other repositories
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release
Walk the llmwiki release process step by step.
ship
Ship is the operational release-prep flow for a connected project repo.