Borrowing it
Nothing to install: this file belongs to VUVAX/press-rank. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/VUVAX/press-rank/main/CLAUDE.mdgit 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/instructions/vuvax/press-rank/claude-md)<a href="https://agentmods.dev/instructions/vuvax/press-rank/claude-md"><img src="https://agentmods.dev/badge/instructions/vuvax/press-rank/claude-md.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.1 | $0.00804 | $0.00804 |
| Opus 5 | $0.00402 | $0.00402 |
| Sonnet 5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
press-rank CLAUDE.md 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PressRank — Claude Code Context
PressRank is a Claude Code plugin for WordPress SEO + GEO article creation. It provides 7 auto-activating skills and 8 /press: commands that move a topic from research to a published, schema-marked WordPress post.
Skills (auto-activate from intent)
| Skill | Role |
|---|---|
wp-article-writer |
Draft WordPress-ready articles with search-intent structure |
keyword-mapper |
Map primary / secondary / semantic keywords across the outline |
geo-optimizer |
Make passages quotable and citable by AI answer engines |
meta-yoast |
Yoast / Rank Math-compatible title + meta description |
schema-builder |
Valid JSON-LD (Article, FAQ, HowTo, Breadcrumb) |
internal-linker |
Contextual internal links, orphan-page fixes |
content-refresher |
Refresh declining posts and re-publish |
Commands (/press:)
/press:research <topic> — keyword + SERP + competitor-gap brief → research/
/press:write <topic> — full SEO + GEO draft → drafts/
/press:optimize <file> — on-page + GEO polish with scored report
/press:meta <file|URL> — title tag, meta description, slug, OG tags
/press:schema <file|URL> — JSON-LD structured data
/press:cluster <topic> — pillar + supporting cluster with link map
/press:audit <file|URL> — SEO score, GEO score, prioritized fixes
/press:publish <file> — push to WordPress via REST API
Operating principles
- WordPress-first output. Every draft maps to REST API fields:
title,slug,excerpt,content,categories,tags, plus Yoast/Rank Math meta. Front matter at the top of each draft carries these fields. - SEO + GEO together. Structure for ranking (intent match, headers, internal links) and for AI citation (answer-first paragraphs, named entities, quotable stats, FAQ blocks).
- Graceful degradation. All skills work with user-provided inputs. Live data (DataForSEO, GSC, GA4, WordPress) is optional and read from a local
.env. - Scoring.
/press:auditreturns an SEO score (0-100) and a GEO citability score (0-100). Aim for SEO ≥ 80 and GEO ≥ 70 before publishing.
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.
- 7d ago First seen · 65 lines · 804 tokens per session scan A b055b14fec34
press-rank CLAUDE.md is an instructions file published in the GitHub repository VUVAX/press-rank (2 stars, last pushed 3mo ago), licensed MIT. It adds 804 tokens to every session, about $0.0040 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.