What is client-legal-safety?

A review guide for legal risks caused by diagnostic targets and network probe hosts shipped in an app. It considers what users may contact or expose in a particular country and requires checking current official law.

Use it when adding or changing diagnostic targets, probe hosts, bootstrap endpoints, or service checks in a client application.

It helps teams avoid shipping diagnostics that could create legal exposure for users or the company, especially when domains or services are politically sensitive or blocked.

How po4yka/RIPDPI configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to po4yka/RIPDPI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/po4yka/RIPDPI/main/.agents/skills/client-legal-safety/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/po4yka/RIPDPI

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/po4yka/ripdpi/client-legal-safety/github.svg)](https://agentmods.dev/skills/po4yka/ripdpi/client-legal-safety)

Your own site

<a href="https://agentmods.dev/skills/po4yka/ripdpi/client-legal-safety"><img src="https://agentmods.dev/badge/skills/po4yka/ripdpi/client-legal-safety/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/po4yka/ripdpi/client-legal-safety"><img src="https://agentmods.dev/badge/skills/po4yka/ripdpi/client-legal-safety.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 713 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00040	$0.00713
Opus 5.5	$0.00016	$0.00285
Sonnet 5.5	$0.00008	$0.00143
Haiku 4.5	$0.00004	$0.00071

Measured yesterday against content hash 64ae7e614dc7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

client-legal-safety 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 yesterday.

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.

.agents/skills/client-legal-safety/SKILL.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Client Legal Safety

Conservative review workflow for what an end user may be exposed to by running the app, enabling a feature, or executing built-in diagnostics. This is about client-side exposure from what ships in the app -- a separate, local-only, gitignored skill (name: legal-check, not present in every checkout) instead reviews public-doc prose for Russian VPN/circumvention advertising-law framing risk. If the task is about wording in a README or public doc rather than which hosts/targets ship, that is the other skill's job.

When To Use

Shipping or editing diagnostics target lists
Adding probe hosts, bootstrap endpoints, or service checks
Deciding whether a blocked or politically sensitive domain should stay in-app
Reviewing client-side risk in a specific jurisdiction

Required Standard

This is a current-law task. Always verify with live sources before concluding that a host or workflow is safe enough to ship.

Prefer primary or official sources:

publication.pravo.gov.ru
prosecutor / regulator / ministry sites (genproc.gov.ru, rkn.gov.ru, etc.)
official statute databases (consultant.ru, garant.ru) when needed for the current text of a law

Use secondary reporting only to locate a designation or enforcement event, then confirm with a primary or official source where possible.

Review Steps

Identify the exact client action:
- passive inclusion in the app
- automatic reachability probe
- manual probe
- DNS lookup only
- service bootstrap / handshake
- download, promotion, or onboarding flow
Enumerate every touched host:
- source generators
- shipped JSON/assets
- service/bootstrap targets
- tests and docs that may reintroduce the host later
Classify each item with a conservative client-risk label:
- safe
- sensitive
- unsafe
- needs_local_counsel
Recommend the lowest-risk product action:
- keep
- keep manual-only
- remove from automatic runs
- remove entirely
- replace with neutral controls

Read the full file on GitHub · 96 lines

Changes

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.

yesterday First seen · 96 lines · 40 tokens per session scan A 64ae7e614dc7

Subscribe to this mod's changes

client-legal-safety is a skill published in the GitHub repository po4yka/RIPDPI (85 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 40 tokens to every session and 713 once invoked, about $0.0002 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-11-07.

Legal and compliance android android-vpn anti-censorship censorship-circumvention deep-packet-inspection dns-over-https

client-legal-safety next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
client-legal-safetypo4yka/RIPDPI	Skill	85	yesterday	BSD-3-Clause	A	40	Claude Code, Codex
app-store-preflight-complianceRevylAI/greenlight	Skill	2.5k	3mo ago	MIT	A	65	Claude Code, Codex
gps-complianceappeeky/google-play-console-cli	Skill	40	18d ago	MIT	A	37	Claude Code, Codex
store-compliance-prokelvinkosbab/AppBootstrapAI	Skill	8	yesterday	MIT	A	117	Claude Code
gplay-compliancePollyGlot/google-play-cli-skills	Skill	5	3d ago	MIT	A	53	Claude Code, Codex
app-store-compliancemjmirza/app-store-compliance	Skill	402	today	none	A	108	Claude Code, Codex
app-store-reviewTalissonVitorino/kmp-ios-skills	Skill	16	2mo ago	MIT	A	219	Claude Code, Codex

RIPDPI: Skill for Claude Code