get-filings

get-filings is a skill for Claude Code from sophymarine/openregistry. It costs 122 tokens per session (712 once invoked), scanned A, original, Apache-2.0.

A tool for listing every document a known company has filed with its national company registry, showing dates, categories, descriptions, and document IDs.

In plain words
What is it for?
Use it to find recent filings, list filings by category, check for annual accounts, or investigate officer changes and other registry submissions.
Why use it?
It provides a filing history without downloading the documents, making it easier to see what a company has submitted and when.

Skill for Claude Code

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

Part of the openregistry plugin — 35 skills, 6 commands, 1 MCP server shipped together

Good fit Use it to find recent filings, list filings by category, check for annual accounts, or investigate officer changes and other registry submissions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sophymarine/openregistry/get-filings
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 sophymarine/openregistry --skill get-filings
Clone the repo
git clone --depth 1 https://github.com/sophymarine/openregistry

Made for: Claude Code.

Or install openregistry, the plugin that ships this one along with the rest of its 35 skills, 6 commands, 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 get-filings

README.md
[![agentmods](https://agentmods.dev/badge/skills/sophymarine/openregistry/get-filings/github.svg)](https://agentmods.dev/skills/sophymarine/openregistry/get-filings)
Your own site
<a href="https://agentmods.dev/skills/sophymarine/openregistry/get-filings"><img src="https://agentmods.dev/badge/skills/sophymarine/openregistry/get-filings/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 get-filings

Your own site · 80×15
<a href="https://agentmods.dev/skills/sophymarine/openregistry/get-filings"><img src="https://agentmods.dev/badge/skills/sophymarine/openregistry/get-filings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 712 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.00122 $0.00712
Opus 5 $0.00061 $0.00356
Sonnet 5 $0.00024 $0.00142
Haiku 4.5 $0.00012 $0.00071

Measured 12d ago against content hash c832d206edff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

get-filings 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 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.

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/get-filings/SKILL.md · 65 lines

How it starts

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

Get Filings

List a company's filings. Metadata only; no document bytes fetched.

When to use

  • "What did Tesla Limited file last year?"
  • "Has Acme filed annual accounts since 2022?"
  • "List all officer-change filings for company X."
  • "Has X filed anything in the last 30 days?"

When NOT to use

  • User wants to extract financial numbers (revenue, profit, etc.) → get-financials (one-shot)
  • User wants directors / shareholders → those have dedicated skills

Example

List the last 10 filings for Tesla Limited (GB 03058989).
List Acme's charge-category filings only.
Has Microsoft Ltd filed any officer changes in the last 90 days?

Workflow

1. If user only gave a name, run find-company first.

2. list_filings({ jurisdiction, company_id, category, limit })
     - category (optional): 'accounts', 'annual-return', 'charges', 'officers',
       'capital', 'insolvency', 'resolution', 'confirmation-statement', or the
       registry's native form code (e.g. AP01, MR01, SH01)
     - limit default 25; max 1000
     - cursor (GB) or offset (IE) for paging beyond one page

3. Optional client-side date filter: keep filings where filing_date >= now - N days.

4. REPORT (newest first):
     filing_date | category | description | document_id | has_document

5. If the user wants the CONTENTS of a specific filing afterwards, follow up with:
     fetch_document({ jurisdiction, document_id })
     (or get-financials if it's the latest accounts and the user wants the numbers extracted)

Edge cases

  • has_document: false: the registry indexes the filing but the body is paywalled or unavailable. Surface explicitly.
  • Pagination styles differ: GB uses opaque cursor (next_cursor); IE uses numeric offset.
  • Native form codes: many jurisdictions use raw form codes (AP01 = appointment, MR01 = mortgage, SH01 = share allotment). Passing them as category works.
  • 501: not all jurisdictions publish a filing index — report the gap honestly.
  • Silence is also a signal: a normally-active company with zero filings in 18+ months is a yellow flag — surface it proactively when the user is building a watchlist.

Read the full file on GitHub · 65 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. 12d ago First seen · 65 lines · 122 tokens per session scan A c832d206edff

Subscribe to this mod's changes

get-filings is a skill published in the GitHub repository sophymarine/openregistry (18 stars, last pushed 5d ago), licensed Apache-2.0. It adds 122 tokens to every session and 712 once invoked, about $0.0006 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.

Related

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…

Hei33enberg/WhiteIntel-OS · 117 tokens

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.

zhanglunet/qcc · 333 tokens

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.

zhanglunet/qcc · 248 tokens

qcc-ownership-trace

A workflow for tracing a company's ownership, including its controlling person, direct shareholders, investments, beneficial owners, and registration changes.

zhanglunet/qcc · 231 tokens

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.

zhanglunet/qcc · 279 tokens

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.

zhanglunet/qcc · 206 tokens