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/accounts)<a href="https://agentmods.dev/commands/sophymarine/openregistry/accounts"><img src="https://agentmods.dev/badge/commands/sophymarine/openregistry/accounts.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.00052 | $0.00433 |
| Opus 5 | $0.00026 | $0.00217 |
| Sonnet 5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
accounts 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
Pull the last $3 year(s) (default 1) of financial statements for "$1" in $2 using OpenRegistry. Every document is returned unmodified — the actual bytes the company filed with the government.
Step 1 — Resolve
search_companies + get_company_profile → canonical company_id.
Step 2 — Access path
FI or KR: use get_financials (native XBRL). Others: list_filings({ category: "accounts", limit: ${3:-1} }) → fetch_document. FR / DE / ES accounts may be behind paid upstream portals — surface alternative_url + cost if paywalled.
Step 3 — Fetch bytes
get_document_metadata + fetch_document for each filing. GB returns XHTML iXBRL (machine-readable via <ix:nonFraction> tags carrying GAAP/IFRS concept URIs); KR returns DS003 fnlttXbrl.xml ZIP; IS returns free PDF.
Step 4 — Extract For each year: Revenue/Turnover · Cost of sales · Gross profit · Operating profit · EBITDA (derive from op profit + D&A) · PBT · Tax · Net income · Total assets · Current/non-current assets · Total/current/non-current liabilities · Equity · Cash · Avg employees · Dividends. Record XBRL concept URIs + currency + thousands/millions flag for every figure.
Step 5 — Deliver Single-year mode: statement with prior-year comparators. Multi-year mode: time series with YoY % changes. Plus: going-concern note, qualified audit opinion flag, micro-entity exemption flag (GB), filing-deadline status.
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 · 25 lines · 52 tokens per session scan A a8327a8d106c
accounts is a command published in the GitHub repository sophymarine/openregistry (17 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 433 once invoked, about $0.0003 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
monitor
AML transaction monitoring and suspicious activity reporting.
risk
Risk reassessment with updated due diligence.
screen
Comprehensive sanctions and PEP screening.
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
scan
Scan AWS account for cost optimization.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…