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 vadim-filimonov/openrater --skill transcribe-filinggit clone --depth 1 https://github.com/vadim-filimonov/openraterWrote 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/vadim-filimonov/openrater/transcribe-filing)<a href="https://agentmods.dev/skills/vadim-filimonov/openrater/transcribe-filing"><img src="https://agentmods.dev/badge/skills/vadim-filimonov/openrater/transcribe-filing/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/vadim-filimonov/openrater/transcribe-filing"><img src="https://agentmods.dev/badge/skills/vadim-filimonov/openrater/transcribe-filing.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.00102 | $0.03073 |
| Opus 5 | $0.00051 | $0.01537 |
| Sonnet 5 | $0.00020 | $0.00615 |
| Haiku 4.5 | $0.00010 | $0.00307 |
Grade A, and why
transcribe-filing 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transcribe a filing into an executable rating plan
You are the transcriber. OpenRater is the calculator. You read documents and fill in a spec'd Excel workbook; the platform deterministically validates it (R-### rules), builds the plan, and rates risks. You never compute premiums yourself, never guess at factors, and never work around a refusal.
Non-negotiable rules
- Review stops. STOP and show the human (with the
open_in_openraterlink where relevant) at each of:- the completed workbook, BEFORE building — tell them to open it in Excel next to the filing;
- any
validate_workbookerrors — list them by R-### and sheet!cell; - the
gaps_and_assumptionsledger, after building; - any failed
test_casesvector — this means the transcription does NOT reproduce the filing; do not use the plan until resolved. Never continue past a stop without an explicit go-ahead.
- Bulk data stays out of the chat. Books and CSVs travel as file paths; report counts and summaries only.
- Record gaps; never approximate. If the filing uses a construct
the capability registry marks unsupported, write it into
gaps_and_assumptionsand keep going. A visible gap beats a wrong number nobody can see. - The user supplies the documents. Never fetch from SERFF or any filing portal yourself — no scraping, ever.
- Filed rates govern. Present results as reconstructions verified against the filing's own worked examples — not as the carrier's official rates.
First run — the three doors (offer once, then never again)
On the user's FIRST substantive OpenRater message of a conversation — when nothing in the conversation shows they've used it before — orient with ONE short menu, then follow their pick. Never re-show the menu in the same conversation; a user who arrives with a filing or a clear ask walks straight through the matching door without seeing a menu at all. (Same behavior in Claude Desktop and Claude Code.)
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 · 231 lines · 102 tokens per session scan A 24d9d402a4f5
transcribe-filing is a skill published in the GitHub repository vadim-filimonov/openrater (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 102 tokens to every session and 3,073 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-31.
Other skills, from other repositories
officecli-financial-model
Use this skill when the user wants to build a financial model — 3-statement model, DCF valuation, LBO, SaaS unit economics, sensitivity / scenario analysis, debt schedule, or fundraising projections — in Excel. Trigger on: 'financial model', '3-statement model', 'P&L + BS + CF', 'DCF', 'WACC', 'NPV', 'terminal value'…
dcf-model
Build discounted cash flow valuation workbooks in Excel.
comps-analysis
Build comparable-company valuation workbooks in Excel.
lbo-model
Build leveraged buyout workbooks with IRR/MOIC in Excel.
excel-author
Build auditable financial workbooks headless via openpyxl.
lbo-model
This skill should be used when completing LBO (Leveraged Buyout) model templates in Excel for private equity transactions, deal materials, or investment committee presentations. The skill fills in formulas, validates calculations, and ensures professional formatting standards that adapt to any template structure.