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.
git 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/commands/sophymarine/openregistry/filings)<a href="https://agentmods.dev/commands/sophymarine/openregistry/filings"><img src="https://agentmods.dev/badge/commands/sophymarine/openregistry/filings.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.1 | $0.00047 | $0.00428 |
| Opus 5 | $0.00023 | $0.00214 |
| Sonnet 5 | $0.00009 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
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 8d 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.
What it actually says
Scan the last $3 days (default 90) of government filings for "$1" in $2 using OpenRegistry. Every filing record is unmodified; every document fetched byte-identical.
Step 1 — Resolve + history
search_companies + get_company_profile → company_id. Then list_filings({ jurisdiction: "$2", company_id, limit: 100 }). Filter client-side to filing_date >= now - ${3:-90} days.
Step 2 — Categorise LOW: accounts, annual-return, confirmation-statement, registered-office · MEDIUM: resolution, conversion, constitution, name-change · HIGH: officers, capital, charges · CRITICAL: insolvency, liquidation, administration.
Step 3 — Fetch HIGH / CRITICAL documents
for each: get_document_metadata + fetch_document. Extract specifics:
- Officer change → name + role + appointment/resignation date
- Charge → chargee/lender + created date + satisfaction status
- Insolvency → type (administration / CVA / CVL / compulsory) + practitioner + hearing date
- Capital → amount + share class + new-external-equity flag
- KR DART pblntf_ty J/E → summarise the rcept_no filing
Step 4 — Timeline + alerts Newest-first with one-line summary + document link. CRITICAL = prominent alert. If no filings: flag the silence (absence itself is a signal).
Step 5 — Register-specific caveats Flag: GB gazette-notice → preludes striking-off. IE B10 = director change. FI LOPP = termination. Report both event date AND filing date (filings can lag events).
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.
- 8d ago First seen · 28 lines · 47 tokens per session scan A 3247411491cc
filings is a command published in the GitHub repository sophymarine/openregistry (17 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 428 once invoked, about $0.0002 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 commands, from other repositories
risk
Risk reassessment with updated due diligence.
screen
Comprehensive sanctions and PEP screening.
monitor
AML transaction monitoring and suspicious activity reporting.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
billing-rate
Gestiona tarifas y facturas de servicios legales. Subcomandos: set (definir tarifa), calculate (calcular honorarios), invoice (generar factura), report (análisis), list (listar tarifas).
child-support-calc
A calculator for Japanese child support and marital living costs, using the revised standard calculation method published in 2019. Child support is money paid for a child after divorce; marital living costs are shared living expenses while spouses live apart.