optimize

A final review command for improving a draft's search-engine structure and its chances of being understood and cited by answer tools. SEO means search-engine optimization; GEO here means optimization for generative-answer systems.

In plain words
What is it for?
Use it on a draft to check titles, metadata, headings, links, keywords, image alt text, readable paragraphs, FAQs, and source-backed statements.
Why use it?
It finds common problems such as weak headings, missing image descriptions, poor keyword placement, and hard-to-scan writing. It also reports scores and explains the changes.

Command

Install

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.

agentmods
npx agentmods add commands/vuvax/press-rank/optimize
Clone the repo
git clone --depth 1 https://github.com/VUVAX/press-rank
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 373 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00373
Opus 5 $0.00007 $0.00187
Sonnet 5 $0.00003 $0.00075
Haiku 4.5 $0.00001 $0.00037

Measured 2d ago against content hash 26b3d8b3462c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

commands/optimize.md · 42 lines

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

  1. 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).
  2. 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.
  3. Readability — short sentences, active voice, scannable lists.
  4. 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.

Changes

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.

  1. 2d ago First seen · 42 lines · 14 tokens per session scan A 26b3d8b3462c

Subscribe to this mod's changes

optimize is a command published in the GitHub repository VUVAX/press-rank (2 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 373 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.

Related

Other commands, from other repositories

auto

Natural-language front door to the marketing pack (narrative/TALE, SEO/GEO/SITE, social/ECHO, email/SEND, Paid Ads/ROAS, influencer/STAR, launch/RAMP). Use when a marketing goal is open-ended or spans disciplines, when it is unclear which skill fits, or for requests like 'help with our marketing', 'grow our traffic'…

aaron-he-zhu/aaron-marketing-skills · 124 tokens

seo-geo

SEO/GEO end-to-end along the SITE loop: survey demand and competitors, implement content, tune quality/tech/on-page, and evaluate authority/rankings/reports/memory (--phase survey|implement|tune|evaluate). Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 58 tokens

narrative

Run a brand-narrative & messaging (TALE) workflow: trace the current message and positioning truth, architect the durable message house/voice/story canon, land it consistently across every surface, and evaluate resonance with tests and drift monitoring. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 59 tokens

email

Run an email-marketing (SEND) workflow: deliverability/consent setup, segmentation, email creative, lifecycle flows, newsletter monetization, send-testing, and the email-quality audit gate. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 50 tokens

influencer

Run an influencer-marketing (STAR) workflow: audience & creator scouting, campaign targeting, briefs, outreach, amplification, and ROI reporting. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 39 tokens

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.

aaron-he-zhu/aaron-marketing-skills · 64 tokens