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 ThomasMoreAI/legal-skills-open --skill apac-transfersgit clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/apac-transfers)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/apac-transfers"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/apac-transfers/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/thomasmoreai/legal-skills-open/apac-transfers"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/apac-transfers.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.00076 | $0.02624 |
| Opus 5.5 | $0.00030 | $0.01050 |
| Sonnet 5.5 | $0.00015 | $0.00525 |
| Haiku 4.5 | $0.00008 | $0.00262 |
Grade A, and why
apac-transfers 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 1mo 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.
This is a copy
94% identical to apac-transfers — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing APAC Cross-Border Transfers
Overview
The Asia-Pacific region encompasses diverse data protection regimes with varying cross-border transfer mechanisms. Unlike the GDPR's unified framework, APAC transfers require navigating multiple overlapping systems: the APEC Cross-Border Privacy Rules (CBPR), ASEAN Model Contractual Clauses (MCCs), and country-specific mechanisms under Japan's APPI, South Korea's PIPA, Thailand's PDPA, and Singapore's PDPA. This skill provides a jurisdiction-by-jurisdiction guide to managing cross-border data flows across the APAC region.
APEC Cross-Border Privacy Rules (CBPR) System
Framework
The APEC CBPR system is a voluntary, accountability-based mechanism enabling participating organisations to demonstrate compliance with internationally recognised privacy protections for cross-border data flows within the APEC region.
Participating economies (as of March 2026): Australia, Canada, Japan, South Korea, Mexico, Philippines, Singapore, Chinese Taipei, United States.
Key features:
- Organisations self-certify compliance with the APEC Privacy Framework principles
- Certification is conducted by an APEC-recognised Accountability Agent (e.g., TRUSTe/TrustArc for the US, JIPDEC for Japan)
- CBPR certification covers only the data flows of the specific certified organisation, not the entire economy
- The Global CBPR Forum (established April 2022) aims to expand the system beyond APEC membership
CBPR Principles
| Principle | Description |
|---|---|
| Preventing Harm | Recognising the interests of the individual regarding the protection of their information |
| Notice | Providing clear and easily accessible statements about data practices |
| Collection Limitation | Limiting personal information collection to that which is relevant |
| Uses of Personal Information | Using personal information only for purposes fulfilling the individual's expectations or as authorised by law |
| Choice | Providing individuals with choice regarding collection, use, and disclosure |
| Integrity of Personal Information | Maintaining the accuracy, completeness, and currency of personal information |
| Security Safeguards | Protecting personal information with appropriate security safeguards |
| Access and Correction | Providing individuals with access to their information and the ability to correct inaccurate data |
| Accountability | Being accountable for complying with measures that give effect to the principles |
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.
- 1mo ago First seen · 184 lines · 76 tokens per session scan A e75e60ac0b57
apac-transfers is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 76 tokens to every session and 2,624 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to apac-transfers, differing in 20 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…