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 indranilbanerjee/digital-marketing-pro --skill region-configgit clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-proWrote 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/indranilbanerjee/digital-marketing-pro/region-config)<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/region-config"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/region-config/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/indranilbanerjee/digital-marketing-pro/region-config"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/region-config.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.00024 | $0.02580 |
| Opus 5.5 | $0.00010 | $0.01032 |
| Sonnet 5.5 | $0.00005 | $0.00516 |
| Haiku 4.5 | $0.00002 | $0.00258 |
Grade A, and why
region-config 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 17d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:region-config
Purpose
Configure regional and market-specific settings for a brand. Sets the timezone for scheduled content delivery, primary language for content generation, applicable compliance and privacy regulations, preferred local platforms, currency for budget and performance reporting, and business hours for communication scheduling. These settings propagate to all downstream commands so that campaigns, content, and reporting automatically respect regional requirements without manual adjustment each time.
This is a setup/configuration command. It writes persistent configuration files that other commands consume. Once a region is configured, commands like /digital-marketing-pro:content-calendar, /digital-marketing-pro:email-sequence, /digital-marketing-pro:paid-advertising, and /digital-marketing-pro:performance-report automatically inherit the region's timezone, language, compliance rules, and platform preferences.
Supports both single-market configurations (e.g., "Japan") and broad regional groupings (e.g., "APAC") depending on how granular the brand's market segmentation needs to be.
Input Required
The user must provide (or will be prompted for):
- Region name: The market being configured — broad region (North America, Europe, APAC, LATAM, MENA) or specific market (Japan, Germany, Brazil, United Kingdom, Australia). Determines which compliance rules, platforms, and defaults apply
- Timezone: IANA timezone identifier — e.g.,
America/New_York,Europe/London,Asia/Tokyo. Used for content scheduling, reporting windows, and business hours calculations - Primary language: The main language for content generation and audience communication in this region — e.g., English (US), English (UK), Japanese, German, Portuguese (BR)
- Secondary languages (optional): Additional languages used in the market for multilingual campaigns — e.g., French and German for Switzerland, English and Mandarin for Singapore
- Currency: ISO 4217 currency code for budget and performance reporting — e.g., USD, EUR, GBP, JPY, BRL. All financial metrics for this region render in this currency
- Local platforms (optional): Region-specific platforms to prioritize — e.g., LINE and Yahoo Japan for Japan, Kakao for South Korea, VK for Russia, WeChat for China, Mercado Libre for LATAM. Overrides global platform defaults for this market
- Business hours (optional): Operating hours for the region in local time — e.g., "09:00-18:00 Mon-Fri". Used to constrain SMS sends, chat responses, and notification timing. Defaults to standard business hours for the timezone if not specified
- Holiday calendar (optional): Region-specific public holidays and observances that affect scheduling — e.g., Golden Week (Japan), Diwali (India), Carnival (Brazil). If omitted, common holidays for the region are applied automatically
- Data residency requirements (optional): Whether data must remain within specific geographic boundaries — relevant for EU, China, Russia, and other jurisdictions with data localization laws
- Industry-specific regulations (optional): Sector-level compliance beyond general privacy laws — e.g., HIPAA for US healthcare, FCA for UK financial services, TGA for Australian therapeutic goods. Adds industry constraints on top of regional compliance rules
- Set as default (optional): Whether this region should become the brand's default region — used when no region is explicitly specified in other commands. Only one region can be the default at a time
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.
- 17d ago Changed · -126 tokens per session 59ea54b3f805
- 1mo ago First seen · 72 lines · 150 tokens per session scan A e5553cadc2a6
region-config is a skill published in the GitHub repository indranilbanerjee/digital-marketing-pro (911 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 2,580 once invoked, about $0.0001 per session on Opus 5.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-09-07.
Other skills, from other repositories
cf-translate
Translate a finished piece into 15 languages, keeping brand voice and citations; literal, adapted or transcreated. "translate this into Spanish".
content-translation
Translate and localize content for international SEO. Use when the user asks to "translate content", "localize my site", "multilingual SEO", "translate to ", "international SEO", "hreflang", "multi-language website", "global content strategy", or wants to expand to new markets.
cf-brief
Write a research-backed content brief from a keyword or topic: intent, competitors, outline. "brief me on this topic".
cf-publish
Publish a reviewed piece to Webflow or WordPress as draft, scheduled or live. "push this live to WordPress".
cf-template
Create a custom content-type template: sections, word counts, citation minimums. "make a template for our case studies".
cf-variants
Generate scored A/B variants of a headline, opening line, hook or CTA, with a test plan. "give me headline options to test".