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/clustergit 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/cluster)<a href="https://agentmods.dev/commands/vuvax/press-rank/cluster"><img src="https://agentmods.dev/badge/commands/vuvax/press-rank/cluster.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.00014 | $0.00307 |
| Opus 5 | $0.00007 | $0.00153 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
cluster 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 4d 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:cluster
Design a hub-and-spoke content cluster so a set of articles reinforce each other's authority.
Input
$ARGUMENTS— the broad pillar topic.
Steps
- Pillar page. Define one comprehensive pillar targeting the head keyword.
- Supporting articles. Identify 6–12 spoke topics, each targeting a long-tail keyword and a distinct search intent. Avoid keyword cannibalization (no two articles targeting the same primary keyword).
- Internal-link matrix. Every spoke links up to the pillar with descriptive anchor text; the pillar links down to each spoke; related spokes cross-link where contextually relevant.
- Priority order. Sequence by opportunity (intent value × gap × feasibility).
Output
Save to research/cluster-<slug>.md:
# Cluster: <pillar topic>
## Pillar
- <title> — head keyword — /url-slug
## Spokes
| # | Title | Primary keyword | Intent | Links to |
|---|-------|-----------------|--------|----------|
## Internal-link map
<spoke → pillar, pillar → spokes, spoke ↔ spoke>
## Build order (priority)
Recommend running /press:write on the pillar first, then each spoke.
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.
- 4d ago First seen · 40 lines · 14 tokens per session scan A 4cf5453b11bc
cluster 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 307 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.