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 vaquarkhan/data-engineering-agent-skills --skill regional-data-compliance-and-sovereigntygit clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-skillsWrote 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/vaquarkhan/data-engineering-agent-skills/regional-data-compliance-and-sovereignty)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/regional-data-compliance-and-sovereignty"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/regional-data-compliance-and-sovereignty/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/vaquarkhan/data-engineering-agent-skills/regional-data-compliance-and-sovereignty"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/regional-data-compliance-and-sovereignty.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.00057 | $0.00746 |
| Opus 5 | $0.00028 | $0.00373 |
| Sonnet 5 | $0.00011 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
regional-data-compliance-and-sovereignty 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regional Data Compliance And Sovereignty
Overview
Use this skill when data obligations differ by jurisdiction, sector, or supervisory authority. It helps agents translate legal and policy requirements into engineering decisions for storage location, transfer boundaries, access, retention, deletion, and audit evidence. This skill is not legal advice; it is the engineering planning layer that should work with legal, privacy, and compliance owners.
When to Use
- operating across
Europe, theUSA,India,Saudi Arabia, or other multi-jurisdiction footprints - handling data residency, sovereignty, or cross-border transfer constraints
- designing controls for
GDPR,PDPL,DPDP, state privacy, or sector-specific obligations - working in regulated sectors where local supervisors such as
SAMAadd extra controls - preparing localized retention, deletion, consent, or breach-evidence paths
Do not assume one global control pattern satisfies every jurisdiction.
Workflow
-
Name the jurisdiction and sector overlays. Include:
- where data subjects or customers are located
- where data is stored and processed
- sector overlays such as finance, health, or public-sector controls
- supervisory bodies or internal policy owners
-
Map cross-border and intra-region data flows. Identify:
- ingestion location
- replication and backup paths
- support and admin access paths
- analytics, ML, and partner-sharing paths
- logs and telemetry containing regulated data
-
Convert obligations into engineering controls. Controls may include:
- regional storage boundaries
- localized encryption and key ownership
- access restrictions by geography or role
- data minimization and masking
- transfer approvals and evidence
- retention and deletion policies by jurisdiction
-
Design the operating model. Decide:
- what can be centralized
- what must stay local
- how regional exceptions are versioned and reviewed
- how incidents and regulator-facing evidence are handled
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 · 83 lines · 57 tokens per session scan A 43a04268bb81
regional-data-compliance-and-sovereignty is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (45 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 746 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
yuwen-publish-precheck
A Chinese-language review workflow for checking content before publishing it on Douyin, Xiaohongshu, or WeChat Channels.
lov-china-website-filing
A workflow for preparing and launching websites in mainland China, including ICP filing and public-security filing. ICP filing is the registration required for many mainland websites, while public-security filing is a separate police registration.
telnyx-email-suppressions-curl
Manage email suppressions (blocks), import and export suppression lists, and manage unsubscribe groups. Use for deliverability compliance and bounce handling.
healthcare-providers-verify
Validates practitioner credentials and license status against the NPI registry. Cross-references specialties, credentials, and practice addresses against official records. Returns Verified / Partially Verified / Unverified / Flagged per practitioner with mismatch details and source URLs. Triggers: "verify these…
python-packaging-license-finder
Use this skill to deterministically find license information for Python packages by checking PyPI metadata first, then falling back to Git repository LICENSE files using shallow cloning.
kafka-connector-review
Review Kafka Connect connector configurations for common misconfigurations using the Lenses MCP server. Checks error handling, DLQ setup, converters, transforms, task count and task health. Use when user says "review connectors", "check connector configs", "why is my connector failing" or asks about Kafka Connect…