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/vuvax/press-rank/schemagit 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/schema)<a href="https://agentmods.dev/commands/vuvax/press-rank/schema"><img src="https://agentmods.dev/badge/commands/vuvax/press-rank/schema.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.00017 | $0.00277 |
| Opus 5 | $0.00009 | $0.00138 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
schema 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 3d 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:schema
Generate JSON-LD structured data that maps to the content and improves both rich results and AI parsing.
Input
$ARGUMENTS— a draft path or URL.
Steps
- Detect applicable schema types from the content:
- Always:
Article(orBlogPosting) +BreadcrumbList. - If a FAQ block exists:
FAQPage. - If step-by-step instructions exist:
HowTo.
- Always:
- Populate from front matter and body — headline, author, datePublished,
image, publisher, and
mainEntityOfPage. - Use placeholders (
https://example.com/...,<Author Name>) for anything not present; never invent author identities or fake review counts. - Validate structure against the templates in
templates/schema/.
Output
A single <script type="application/ld+json"> block ready to paste into the
WordPress post (or inject via the publisher). Note any field the user must fill
in before going live.
Do not generate
Review/AggregateRatingschema unless real, verifiable ratings exist — fabricated ratings violate Google's guidelines.
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.
- 3d ago First seen · 32 lines · 17 tokens per session scan A 6a8d87d95acc
schema is a command published in the GitHub repository VUVAX/press-rank (2 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 277 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
engagement
Run a marketing engagement using the 12-Part methodology. Subcommands: start, next, status, validate, re-run-decision, update-back, lif-show, file-tree, list-engagements, four-core, growth-plan, yearly-planner, loop.
resume
Resume a long-running DMP workflow (engagement / campaign-plan / content-engine / seo-audit / competitor-analysis / campaign-audit / launch-campaign) that was interrupted partway through.
execute-action
Actually fire a campaign-audit / launch-campaign action against its real API (vs returning a manifest). Reads credentials from env vars (no OAuth flow). Read ops auto-execute with --execute; write ops require --confirm. Logs every execution to the audit trail.
output-folder
Print + open the user-visible DMP output folder for a brand (/Documents/DigitalMarketingPro/{brand}/). Direct answer to "where did my engagement deliverables save?".
doctor
Per-action readiness diagnostic. Shows which campaign-audit and launch-campaign actions are live (manifest-ready) vs blocked (stub-unconfigured) in the current environment, with one-step setup hints for the blocked ones. Now includes model-registry freshness + Cowork+Drive routing status.
status
Unified status snapshot of the active brand: profile, engagements, recent insights, recent compliance violations, Python dependency mode.