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 sophymarine/openregistry --skill get-shareholder-detailsgit clone --depth 1 https://github.com/sophymarine/openregistryWrote 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/sophymarine/openregistry/get-shareholder-details)<a href="https://agentmods.dev/skills/sophymarine/openregistry/get-shareholder-details"><img src="https://agentmods.dev/badge/skills/sophymarine/openregistry/get-shareholder-details/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/sophymarine/openregistry/get-shareholder-details"><img src="https://agentmods.dev/badge/skills/sophymarine/openregistry/get-shareholder-details.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.00103 | $0.00646 |
| Opus 5 | $0.00051 | $0.00323 |
| Sonnet 5 | $0.00021 | $0.00129 |
| Haiku 4.5 | $0.00010 | $0.00065 |
Grade A, and why
get-shareholder-details 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get Shareholder Details
Statutory shareholder / member / quota-holder roster of one company.
When to use
- "Who owns Tesla Limited?"
- "List the shareholders of company SC123456."
- "Show me the members register for Acme."
- "Who holds equity in Norwegian organisation 923609016?"
When NOT to use
- User asks for "beneficial owner", "ultimate beneficial owner", "PSC", or "UBO" — that is a SEPARATE statutory register that OpenRegistry's current tool set does NOT expose. Tell the user honestly.
- User wants directors →
get-director-details - User wants a filing that carries the share register →
get-filings({ category: 'capital' })
Example
Who owns Norwegian company 923609016?
Show me the members of GB 03058989.
Workflow
1. If user only gave a name, run find-company first to capture company_id.
2. get_shareholders({ jurisdiction, company_id })
3. REPORT:
- Each shareholder: name (or corporate name) | shares (% or count or class) | capital allocated
- Surface the disclosure flag explicitly: did this legal form publish, or did the
registry return a pointer to a separate filing?
- If the response carries a `document_id`, mention it can be fetched via fetch_document.
- If empty: say "not publicly disclosed for this legal form" — do NOT say "no shareholders".
Edge cases
- Shareholders ≠ PSC / UBO: shareholders = statutory equity roster. PSC / UBO = beneficial-ownership register on a >25% control threshold. The two can disagree (a 10% shareholder is on the members register but not the PSC register; a corporate nominee can be a PSC without appearing on the members register). OpenRegistry currently exposes the SHAREHOLDER register only.
- Joint-stock / public-limited forms: typically keep shareholders in a private book; the public register returns empty. That emptiness is meaningful — surface it.
- Pointer to filing: some registries return a
document_idpointing at the filing carrying the live share roster; chain to fetch_document. - 501: not every jurisdiction publishes shareholders.
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.
- 11d ago First seen · 57 lines · 103 tokens per session scan A 3d387489d1f5
get-shareholder-details is a skill published in the GitHub repository sophymarine/openregistry (17 stars, last pushed 4d ago), licensed Apache-2.0. It adds 103 tokens to every session and 646 once invoked, about $0.0005 per session on Opus 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-08-30.
Other skills, from other repositories
corporate-ownership-investigation
Trace who ultimately owns or controls a company, screen it for sanctions, and report the result without overclaiming. Use when asked "who owns X", "who is behind X", "is X sanctioned", "is X connected to Y", "what does X own", or when doing KYC/AML/due-diligence, counterparty checks, supply-chain screening, or…
qcc-executive-background
A Chinese company and executive background-check workflow examines a named person together with a company's Unified Social Credit Code, the identifier used for Chinese businesses.
qcc-risk-screen
A full risk-screening workflow for Chinese companies using Qichacha, a business-information service. It checks legal, enforcement, tax, bankruptcy, ownership, operating, and other company-risk records.
qcc-basic-profile
A workflow for Qichacha, a Chinese company-information service, that gathers a basic business summary in one pass. It covers registration, contacts, key people, tax and invoice details, branches, listings, and annual reports.
qcc-ipr-portfolio
A Chinese-language workflow for listing a company's intellectual-property and online assets. It covers patents, trademarks, copyrights, integrated-circuit layouts, standards, licenses, websites, apps, online shops, and social-media accounts.
qcc-ownership-trace
A workflow for tracing a company's ownership, including its controlling person, direct shareholders, investments, beneficial owners, and registration changes.