sanctions-screening-guide

sanctions-screening-guide is a skill for Claude Code from cyanheads/sanctions-screening-mcp-server. It costs 55 tokens per session (765 once invoked), scanned A, original, Apache-2.0.

A guide for checking whether a person or organization may be subject to sanctions or export controls. It explains how to confirm identity, investigate ownership, compare possible matches, and report gaps in the search.

In plain words
What is it for?
It helps with counterparty due diligence, ownership-chain research, sanctions screening, and reviewing possible designation matches without merging uncertain identities.
Why use it?
Names can match several legal entities, and incomplete searches or ownership records can lead to false conclusions about a counterparty.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the sanctions-screening-mcp-server plugin — 35 skills, 1 MCP server shipped together

Good fit It helps with counterparty due diligence, ownership-chain research, sanctions screening, and reviewing possible designation matches without merging uncertain identities.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cyanheads/sanctions-screening-mcp-server/sanctions-screening-guide
Install

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.

Any agent
npx skills add cyanheads/sanctions-screening-mcp-server --skill sanctions-screening-guide
Clone the repo
git clone --depth 1 https://github.com/cyanheads/sanctions-screening-mcp-server

Made for: Claude Code.

Or install sanctions-screening-mcp-server, the plugin that ships this one along with the rest of its 35 skills, 1 MCP server.

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.

agentmods badge for sanctions-screening-guide

README.md
[![agentmods](https://agentmods.dev/badge/skills/cyanheads/sanctions-screening-mcp-server/sanctions-screening-guide/github.svg)](https://agentmods.dev/skills/cyanheads/sanctions-screening-mcp-server/sanctions-screening-guide)
Your own site
<a href="https://agentmods.dev/skills/cyanheads/sanctions-screening-mcp-server/sanctions-screening-guide"><img src="https://agentmods.dev/badge/skills/cyanheads/sanctions-screening-mcp-server/sanctions-screening-guide/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.

agentmods 80×15 button for sanctions-screening-guide

Your own site · 80×15
<a href="https://agentmods.dev/skills/cyanheads/sanctions-screening-mcp-server/sanctions-screening-guide"><img src="https://agentmods.dev/badge/skills/cyanheads/sanctions-screening-mcp-server/sanctions-screening-guide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 765 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.00765
Opus 5.5 $0.00022 $0.00306
Sonnet 5.5 $0.00011 $0.00153
Haiku 4.5 $0.00006 $0.00076

Measured 5d ago against content hash e17a09c8128d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sanctions-screening-guide 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 5d 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.

skills/sanctions-screening-guide/SKILL.md · 31 lines

How it starts

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

Gates

Before attributing an ownership graph to a counterparty, compare the candidate GLEIF record with the identity evidence supplied: jurisdiction, registration authority and number, and addresses. A ranked name match alone does not choose the legal entity. If competing records remain plausible, retain the alternatives and ask for identifying evidence; do not merge their ownership chains into one counterparty.

Before treating a search as exhausted, distinguish an empty page from an empty result set and a finished result set from a bounded candidate search. Drain available pages; where the search reports a lower bound, narrow with another identifying name word or a known jurisdiction. If an entity is absent under the default registration-status filter, broaden the status search before concluding it was not found. An unavailable alternate-name index is a coverage gap, not evidence that a trading or former name has no LEI.

Before using a designation to identify a person or organization, compare the published identifiers and corroborating details. Preserve partial or approximate birth dates; do not pair separate dates and birthplaces unless the record pairs them. Descriptive features can corroborate a candidate but are not searchable identifiers. Keep source-specific labels and units: similar feature names do not establish equivalent measurements. A CSL record with unknown entity type remains unknown; neither its list membership nor an end date establishes its current legal effect. Verify export-control restrictions against the named agency list and Federal Register material, using the published provenance when available.

Workflows

Finish an ownership investigation

Drain continuation pages for the same ownership segment before following its boundary records. Assemble nodes by LEI and edges by child LEI, parent LEI, and relationship type; an edge may refer to a node returned on another page. For each omitted branch, start a new trace at the boundary LEI on its specified walk side. Track already-processed LEI/side pairs to avoid cycles and overlapping work. Segment depth restarts at the new root; retain the original segment's node placement rather than treating the new depth as distance from the original counterparty.

Read the full file on GitHub · 31 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.

  1. 5d ago First seen · 31 lines · 55 tokens per session scan A e17a09c8128d

Subscribe to this mod's changes

sanctions-screening-guide is a skill published in the GitHub repository cyanheads/sanctions-screening-mcp-server (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 55 tokens to every session and 765 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-02.

Related

sanctions-screening-guide compared with skills from other repositories

sanctions-screening-guide next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
sanctions-screening-guidecyanheads/sanctions-screening-mcp-serverSkill36d agoApache-2.0A55Claude Code
regtech-expertpersonamanagmentlayer/pclSkill4412d agoApache-2.0A73Claude Code
risk-assessmentvyayasan/kyc-analystSkill614mo agoMITA81Claude Code
transaction-monitoringvyayasan/kyc-analystSkill614mo agoMITA47Claude Code
onboardingvyayasan/kyc-analystSkill614mo agoMITA83Claude Code
screeningvyayasan/kyc-analystSkill614mo agoMITA44Claude Code
refreshvyayasan/kyc-analystSkill614mo agoMITA74Claude Code