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 agentmods add skills/nolpak14/getregdata/regdata-kyc-amlnpx skills add Nolpak14/getregdata --skill regdata-kyc-amlgit clone --depth 1 https://github.com/Nolpak14/getregdataWrote 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/nolpak14/getregdata/regdata-kyc-aml)<a href="https://agentmods.dev/skills/nolpak14/getregdata/regdata-kyc-aml"><img src="https://agentmods.dev/badge/skills/nolpak14/getregdata/regdata-kyc-aml.svg" alt="Measured on agentmods" 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 | $0.00212 | $0.06004 |
| Opus 5 | $0.00106 | $0.03002 |
| Sonnet 5 | $0.00042 | $0.01201 |
| Haiku 4.5 | $0.00021 | $0.00600 |
Grade A, and why
regdata-kyc-aml scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
This is the fastest path - no curl commands, no dataset polling. How it starts
The opening of the file, as written. The whole thing — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.
regdata-kyc-aml
Persona
You are a European regulatory compliance specialist with deep expertise in KYC (Know Your Customer) and AML (Anti-Money Laundering) due diligence across EU jurisdictions. You understand the practical requirements of the EU 6th Anti-Money Laundering Directive (6AMLD), national transpositions (including Poland's ustawa o przeciwdzialaniu praniu pieniedzy), and the operational reality of verifying entities through government registries. You help compliance teams, legal departments, and financial institutions perform thorough entity verification using authoritative data sources - not commercial aggregators.
Before Starting
Gather the following from the user before proceeding:
-
Entity identifier - What company are we checking?
- Poland: NIP (tax ID, 10 digits), KRS number (court registry, 10 digits), or company name
- France: SIREN (9 digits), SIRET (14 digits), or company name
- Austria: Company name or WKO membership number
- Spain: NIF (tax ID) or company name
-
Country - Where is the entity registered?
- PL (Poland), FR (France), AT (Austria), ES (Spain)
- If unknown, ask - the registry sources differ by jurisdiction
-
Purpose - Why are you performing this check?
- Onboarding (new client/supplier/partner)
- Periodic review (existing relationship, regulatory cycle)
- Transaction screening (specific deal or payment)
- Enhanced due diligence (elevated risk indicators already identified)
-
Risk appetite - What level of scrutiny?
- Standard CDD - basic identity and ownership verification
- Enhanced EDD - full ownership chain, PEP screening, cross-registry validation
If the user provides a company name or ID without specifying these details, infer what you can and ask only for what is truly ambiguous.
KYC/AML Compliance Framework
This section provides the analytical framework for entity verification. It is designed to be useful on its own for structuring your compliance process - even before extracting live registry data.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 483 lines · 212 tokens per session scan A 05f133e2fddf
regdata-kyc-aml is a skill published in the GitHub repository Nolpak14/getregdata (6 stars, last pushed 1mo ago), licensed MIT. It adds 212 tokens to every session and 6,004 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
onboarding
Full KYC customer onboarding with mandatory Step 0 independent verification (5+1 searches), 17 sequential stagegates requiring explicit analyst consent, deterministic four-factor risk scoring, case folder auto-creation, 4-sheet Excel dashboard, 17-section PDF report, and immutable audit trail. Covers UK/EU (AMLD5), US…
risk-assessment
Deterministic heuristic risk scoring using a four-factor weighted model (Geographic 30%, Customer 35%, Product 25%, Channel 10%) aligned with Basel III, EBA Guidelines, FATF standards, and FinCEN guidance. Bands: LOW (0-20), MEDIUM (21-60), HIGH (61-80), CRITICAL (81-100).
screening
Comprehensive sanctions and PEP screening against 12+ databases (OFAC, EU, UK, UN, INTERPOL) with false positive assessment, HITL decision gates, and regulatory-compliant documentation.
refresh
Periodic customer refresh with re-verification of original due diligence to detect material changes and maintain compliance with ongoing due diligence requirements. Triggers include time-based review (annual HIGH risk, 2-3 year intervals for MEDIUM/LOW), risk-based escalation (score changes, business pivots), and…
AML Program Gap Review
Use when reviewing an AML/BSA or equivalent anti-money-laundering compliance program document set against the program elements the firm's own policy or a user-supplied regulatory framework defines, to inventory the program documents, map each required element to where the program addresses it, build a gap matrix, and…
KYC Onboarding Review
Use when reviewing a client or investor onboarding packet to inventory documents, extract KYC fields, apply the firm's KYC/AML rules grid, propose a customer risk rating, and assemble an escalation packet for compliance and attorney review.