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.
git clone --depth 1 https://github.com/VUVAX/press-rankWrote 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/vuvax/press-rank/publish)<a href="https://agentmods.dev/commands/vuvax/press-rank/publish"><img src="https://agentmods.dev/badge/commands/vuvax/press-rank/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.1 | $0.00013 | $0.00415 |
| Opus 5 | $0.00006 | $0.00208 |
| Sonnet 5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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 7d 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
/press:publish
Push a finished draft to WordPress with title, content, taxonomy, and SEO meta.
Prerequisites
A local .env (copy templates/.env.example) with:
WP_BASE_URL=https://your-site.com
WP_USERNAME=your-wp-user
WP_APP_PASSWORD=xxxx xxxx xxxx xxxx # WordPress Application Password, NOT your login password
The app password is read locally and never printed or committed.
Input
$ARGUMENTS— path to the draft to publish.
Steps
- Pre-flight. Confirm the draft passed
/press:audit(SEO ≥ 80, GEO ≥ 70). If not, warn and ask before continuing. - Map fields from front matter to the REST payload:
title→title- body Markdown → rendered
content(HTML) slug→slugmeta_description→ Yoast (_yoast_wpseo_metadesc) or Rank Math metacategories/tags→ resolve to term IDs (create if missing, with confirm)schema→ inject JSON-LD into the post body or header
- Default to
status: draftin WordPress unless the user explicitly asks to publish live. Always confirm before settingstatus: publish. - POST to
"$WP_BASE_URL/wp-json/wp/v2/posts"using HTTP Basic auth with the application password.
Output
Report the created post ID, edit URL, and live/preview URL. On failure, surface the REST error (status + message) without echoing credentials.
Safety
- Never overwrite an existing post without confirming the target ID.
- Publishing live is an outward-facing action — confirm first every time.
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.
- 7d ago First seen · 44 lines · 13 tokens per session scan A f1ea187dbfb1
publish is a command published in the GitHub repository VUVAX/press-rank (2 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 415 once invoked, about $0.0001 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-31.
Other commands, from other repositories
launch
Run a product-launch (RAMP) workflow: positioning and launch tiering, window/early-access design, message house and asset kits, the launch-readiness gate with a T-1 go/no-go, launch-day execution, and the post-launch prove loop. Not sure? Use /aaron-marketing:auto.
status
Unified status snapshot of the active brand: profile, engagements, recent insights, recent compliance violations, Python dependency mode.
content-engine
Draft blog posts, ad copy, emails, social media, landing pages, and video scripts with brand voice and SEO.
performance-report
Generate a marketing performance report with KPI tracking, trend analysis, anomaly detection, and recommendations.
backlink-gap
Find domains linking to your competitors but not to you, ranked by priority score (DR + link-overlap + traffic + topical relevance) with a four-gate quality scorecard.
seo-drift
Compare two SEO snapshots (GSC / GSC AI Performance / rank tracker / AEO probe) and surface top movers per metric with auto-classification — growth / decline / reshuffle / stable / new / lost.