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 skills add VUVAX/press-rank --skill keyword-mappergit 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/skills/vuvax/press-rank/keyword-mapper)<a href="https://agentmods.dev/skills/vuvax/press-rank/keyword-mapper"><img src="https://agentmods.dev/badge/skills/vuvax/press-rank/keyword-mapper/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/skills/vuvax/press-rank/keyword-mapper"><img src="https://agentmods.dev/badge/skills/vuvax/press-rank/keyword-mapper.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.00037 | $0.00436 |
| Opus 5 | $0.00018 | $0.00218 |
| Sonnet 5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
keyword-mapper 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 9d 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
Keyword Mapper
Turns a keyword set into a placement plan across an outline so coverage is complete without stuffing.
Quick start
Map these keywords across my outline: <keywords> / <outline>
Instructions
-
Classify intent for each keyword: informational, commercial, transactional, or navigational.
-
Assign roles:
- Primary — one per article. Owns the H1 and the page's core promise.
- Secondary — 3–6 closely related terms, each owning a section.
- Semantic / LSI — supporting terms woven into body copy for topical depth.
-
Placement rules for the primary keyword: H1, first 100 words, at least one H2, image alt text, and the conclusion. Keep total density ≤ 2%.
-
Cannibalization guard. If two URLs/sections target the same primary keyword, flag it and recommend consolidating or re-targeting one.
-
Output a map:
| Section (H2/H3) | Keyword | Role | Intent | |-----------------|---------|------|--------|
Next best skill
wp-article-writer to draft against the map, or internal-linker for anchors.
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.
- 9d ago First seen · 52 lines · 37 tokens per session scan A e042e8fd76cd
keyword-mapper is a skill published in the GitHub repository VUVAX/press-rank (2 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 436 once invoked, about $0.0002 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 skills, from other repositories
gingiris-seo-geo-agent
SEO/GEO Agent Operations SOP v2 — Rebuilt from real-world operations (analook.com 0→launch, GSC incident, DataForSEO monitoring, gingiris.tools post-migration recovery). What's new in v2: • Step-by-step onboarding (Q1→Q6), multiple choice wherever possible — no big forms • Mandatory daily SEO log — first item is…
blog-post
Use this skill when writing blog posts, articles, or long-form web content—from quick how-to guides to in-depth opinion pieces. Trigger phrases: 'write a blog post about', 'draft an article on', 'create a post for my blog'. Do NOT use for academic papers, news reporting, or content requiring real-time facts.
Blog Post Writer
Create engaging, SEO-optimized blog posts for any industry or topic.
Blog Post Writer
Create engaging, SEO-optimized blog posts for any industry or topic.
content-amplifier
Use when the user asks to "amplify influencer content with paid media", "set up whitelisting or Spark Ads", "decide which posts to boost", "repurpose influencer content", "turn one video into multiple ads", or "build a UGC asset library"; produces (paid mode) a content-selection scorecard, a paid amplification…
inbox-placement-monitor
Use when the user asks to "track where my emails are actually landing after I send", "read my seed-list inbox vs spam vs promotions results", "trend my Gmail Postmaster / Microsoft SNDS reputation", or "did placement drop after my last send"; produces a per-provider inbox/spam/promotions placement read, a domain/IP…