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/optimize)<a href="https://agentmods.dev/commands/vuvax/press-rank/optimize"><img src="https://agentmods.dev/badge/commands/vuvax/press-rank/optimize/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/commands/vuvax/press-rank/optimize"><img src="https://agentmods.dev/badge/commands/vuvax/press-rank/optimize.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.00014 | $0.00373 |
| Opus 5.5 | $0.00006 | $0.00149 |
| Sonnet 5.5 | $0.00003 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
optimize 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.
What it actually says
/press:optimize
Polish an existing draft and report what changed and why.
Input
$ARGUMENTS— path to a draft (e.g.drafts/<slug>.md).
Steps
- On-page pass (see
references/seo-checklist.md):- Title ≤ 60 chars, meta description ≤ 155 chars, one H1.
- Logical H2/H3 hierarchy, descriptive anchor text.
- Primary keyword placement (H1, intro, ≥1 H2, conclusion).
- Image alt text present and descriptive.
- Internal-link suggestions (delegate to
internal-linker).
- GEO pass (see
references/geo-citability.md):- Answer-first paragraphs; one idea per paragraph.
- Quotable, self-contained sentences with sources.
- FAQ block and entity coverage.
- Readability — short sentences, active voice, scannable lists.
- Score — compute SEO (0-100) and GEO citability (0-100).
Output
Edit the draft in place, then print a short report:
SEO score: 82/100 (was 64)
GEO score: 71/100 (was 48)
Changes:
- Tightened title to 57 chars
- Added FAQ block (4 Q&A)
- Added 3 internal-link suggestions
Remaining (optional):
- Add an original data point or screenshot for E-E-A-T
Recommend /press:meta and /press:schema next, then /press:audit as the gate.
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 · 42 lines · 14 tokens per session scan A 26b3d8b3462c
optimize is a command published in the GitHub repository VUVAX/press-rank (2 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 373 once invoked, about $0.0001 per session on Opus 5.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.
new-client
Scaffold a new client project — folders, client.yml, CLAUDE.md — then interview for the essentials and fill the profile.
monthly-report
Generate and render the monthly client report via the report-generator skill; schedulable with /loop or /schedule.
competitor-watch
Weekly competitor monitoring — diff this week's competitor snapshots against last week and recommend 48-hour responses.
growth-plan
Turn diagnosis into a sized greenfield opportunity map + a sequenced, mechanism-driven capture plan to overtake competitors.
excalibur-blog-run
A command that runs a complete Excalibur BLOG article process through an orchestrator and supporting agents.