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 Nolpak14/getregdata --skill gleif-lei-lookupgit 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/gleif-lei-lookup)<a href="https://agentmods.dev/skills/nolpak14/getregdata/gleif-lei-lookup"><img src="https://agentmods.dev/badge/skills/nolpak14/getregdata/gleif-lei-lookup/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/nolpak14/getregdata/gleif-lei-lookup"><img src="https://agentmods.dev/badge/skills/nolpak14/getregdata/gleif-lei-lookup.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.00170 | $0.02124 |
| Opus 5 | $0.00085 | $0.01062 |
| Sonnet 5 | $0.00034 | $0.00425 |
| Haiku 4.5 | $0.00017 | $0.00212 |
Grade A, and why
gleif-lei-lookup 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 12d 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.
curl -H 'User-Agent: getregdata-skill' \ How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gleif-lei-lookup
Free, global entity resolution from the official GLEIF API. This is the spine of cross-border company work: it turns a messy company name into a canonical LEI, tells you the entity's local registry ID and country, and maps its legal parent/child structure - so you can then pull the deep national data from the right source. No API key, no Apify token.
Persona
You are an entity-resolution and corporate-structure analyst. Given a name that may be spelled inconsistently, you find the one authoritative legal entity, confirm it is active, place it in its corporate group (subsidiary or ultimate parent), and hand off the local registry identifier so a national registry lookup can go straight to the right record.
What this gives you (for free)
- LEI record - the 20-character LEI, official legal name, legal form, legal address, and entity status (ACTIVE / INACTIVE).
- Local registry ID -
entity.registeredAs: the entity's identifier in its home registry (e.g. a Companies House number, an HRB number, a KRS/NIP). This is the join key into national sources. - Registration health -
registration.status(ISSUED / LAPSED / RETIRED) and next renewal date. A LAPSED LEI is a signal the entity stopped maintaining it. - Corporate structure - direct parent, ultimate parent, direct/ultimate children, and managed funds, at the accounting-consolidation level.
Data is CC0 1.0 (public domain) - free for any use, including commercial. The only rule: do not imply GLEIF endorsement.
Authentication
None. No key, no registration. Be polite: send a descriptive User-Agent and stay under ~60 requests/minute (over that returns 429).
API reference
Base URL: https://api.gleif.org/api/v1/ - responses are JSON:API (application/vnd.api+json).
| # | Purpose | Method + path | Example |
|---|---|---|---|
| 1 | Fuzzy name autocomplete | GET /fuzzycompletions?field=entity.legalName&q={name} |
/fuzzycompletions?field=entity.legalName&q=apple |
| 2 | Filtered / full-text search | GET /lei-records?filter[entity.legalName]={name}&page[size]=10 |
/lei-records?filter[entity.legalName]=Apple |
| 3 | Look up by LEI | GET /lei-records/{lei} |
/lei-records/HWUPKR0MPOU8FGXBT394 |
| 4 | Direct parent | GET /lei-records/{lei}/direct-parent |
|
| 5 | Ultimate parent | GET /lei-records/{lei}/ultimate-parent |
|
| 6 | Children / funds | GET /lei-records/{lei}/direct-children , /ultimate-children , /managed-funds |
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.
- 12d ago First seen · 123 lines · 170 tokens per session scan A cfe890fe0900
gleif-lei-lookup is a skill published in the GitHub repository Nolpak14/getregdata (6 stars, last pushed 1mo ago), licensed MIT. It adds 170 tokens to every session and 2,124 once invoked, about $0.0009 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
regtech-expert
Expert in regulatory technology, compliance automation, KYC/AML, transaction monitoring, risk assessment, and automated reporting. Use when the user mentions compliance, KYC, AML, transaction monitoring, risk assessment, or regulatory reporting, or when the task involves KYC/AML Compliance, KYC/AML Program, Regulatory…
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…