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 PavloSEO/seohead-seotools --skill regional-auditgit clone --depth 1 https://github.com/PavloSEO/seohead-seotoolsWrote 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/pavloseo/seohead-seotools/regional-audit)<a href="https://agentmods.dev/skills/pavloseo/seohead-seotools/regional-audit"><img src="https://agentmods.dev/badge/skills/pavloseo/seohead-seotools/regional-audit/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/pavloseo/seohead-seotools/regional-audit"><img src="https://agentmods.dev/badge/skills/pavloseo/seohead-seotools/regional-audit.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.00146 | $0.01294 |
| Opus 5 | $0.00073 | $0.00647 |
| Sonnet 5 | $0.00029 | $0.00259 |
| Haiku 4.5 | $0.00015 | $0.00129 |
Grade A, and why
regional-audit 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 10d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regional Audit — Cities, Subdomains, and Satellite Sites
Regional targeting in the Russian-language web is implemented using three mutually incompatible approaches. Half of the resulting problems come from choosing an approach without considering the consequences or from mixing two approaches at once.
| Approach | Example | Region in Yandex Webmaster | Cost of a Mistake |
|---|---|---|---|
| Subdomain | msk.example.com |
one per host | each city needs its own content |
| Directory | example.com/msk/ |
one for the entire website | the city is established only through page text |
| Satellite site | example-msk.example |
its own region, but also its own authority | sites may be grouped as affiliates |
The key point people confuse is that directories have one Yandex Webmaster region for
the entire domain. You cannot assign Moscow to /msk/ and Saint Petersburg to /spb/.
Directories work only through the text on the page. Subdomains are separate hosts, and
each host can be assigned its own region.
When to Use It
- A client has “branches throughout Russia,” but traffic comes from only one city.
- Before selecting a regional SEO approach, to avoid rebuilding the structure later.
- When satellite sites exist and you need to determine whether Yandex may group them as affiliates.
- Regional pages exist but do not rank, and the reason is unclear.
Workflow
Step 1. Capture the structure. The tool automatically finds the city switcher on the page:
seohead regions-check --url https://example.com
Step 2. Add what cannot be seen on the page. Satellite sites on separate domains are almost never included in a city switcher, so always supply them manually:
seohead regions-check --url https://example.com --extra "https://example-msk.example/,https://example-spb.example/" --limit 20
Step 3. Read findings. Their order roughly corresponds to severity:
| Finding | What It Means |
|---|---|
| “redirect to the main site” | the region does not actually exist: there is a host but no page |
| “canonicalized to another host” | the page has removed itself from the index |
| “noindex on regional pages” | the same outcome, but explicit |
| “content matches” | cities differ only by address, causing cannibalization |
| “identical title” | the city is not inserted into the title |
| “same telephone number in every region” | a signal to Yandex that the branches do not exist |
| “two approaches at once” | subdomains and directories compete with one another |
| “on separate domains” | check for affiliate grouping manually |
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.
- 10d ago First seen · 103 lines · 146 tokens per session scan A 0b13fe02ece9
regional-audit is a skill published in the GitHub repository PavloSEO/seohead-seotools (0 stars, last pushed 7d ago), licensed MIT. It adds 146 tokens to every session and 1,294 once invoked, about $0.0007 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
page-metadata
When the user wants to optimize meta tags other than title, description, Open Graph, or Twitter Cards. Also use when the user mentions "hreflang," "meta robots," "viewport," "charset," "canonical meta," "other meta tags," "meta robots noindex," "meta robots nofollow," "hreflang tags," "viewport meta," or "meta…
translation
When the user wants to translate content, create translation workflows, manage terminology, or optimize translation quality. Also use when the user mentions "translate," "translation," "localization copy," "glossary," "terminology," "style guide translation," "machine translation," "human translation," "TMS," or…
localization-strategy
When the user wants to plan or implement localization strategy for multilingual and global growth. Also use when the user mentions "localization," "multilingual," "i18n," "global expansion," "market entry," "localization strategy," "hreflang," "multi-language SEO," or "international SEO." For translation workflow…
hreflang-international
International / multilingual SEO audit focused on hreflang correctness. Detects and diagnoses the most common (and ranking-damaging) hreflang mistakes: missing or broken return tags, wrong language/region codes, missing x-default, self-referencing errors, conflicts between hreflang and canonical, and inconsistent…
region-config
Configure a brand's regional settings — timezone, languages, currency, compliance regulations (GDPR, CCPA, APPI, LGPD, EU AI Act Article 50, and more), local platforms, business hours, holiday calendars, and data-residency rules — written to a persistent per-region config file plus a practical compliance checklist.…
language-config
Configure the brand's multilingual settings in profile.json — primary and secondary languages, do-not-translate terms, preferred translation service per language (routed by language family across the translation MCPs you have connected), and locale formatting for dates, numbers, and currency — with…