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 agentmods add skills/thevibeworks/claude-code-docs/analyzing-financial-statementsnpx skills add thevibeworks/claude-code-docs --skill analyzing-financial-statementsgit clone --depth 1 https://github.com/thevibeworks/claude-code-docsWhat 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 | $0.00023 | $0.00506 |
| Opus 5 | $0.00012 | $0.00253 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
analyzing-financial-statements 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 3d 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.
This is a copy
100% identical to analyzing-financial-statements — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Financial Ratio Calculator Skill
This skill provides comprehensive financial ratio analysis for evaluating company performance, profitability, liquidity, and valuation.
Capabilities
Calculate and interpret:
- Profitability Ratios: ROE, ROA, Gross Margin, Operating Margin, Net Margin
- Liquidity Ratios: Current Ratio, Quick Ratio, Cash Ratio
- Leverage Ratios: Debt-to-Equity, Interest Coverage, Debt Service Coverage
- Efficiency Ratios: Asset Turnover, Inventory Turnover, Receivables Turnover
- Valuation Ratios: P/E, P/B, P/S, EV/EBITDA, PEG
- Per-Share Metrics: EPS, Book Value per Share, Dividend per Share
How to Use
- Input Data: Provide financial statement data (income statement, balance sheet, cash flow)
- Select Ratios: Specify which ratios to calculate or use "all" for comprehensive analysis
- Interpretation: The skill will calculate ratios and provide industry-standard interpretations
Input Format
Financial data can be provided as:
- CSV with financial line items
- JSON with structured financial statements
- Text description of key financial figures
- Excel files with financial statements
Output Format
Results include:
- Calculated ratios with values
- Industry benchmark comparisons (when available)
- Trend analysis (if multiple periods provided)
- Interpretation and insights
- Excel report with formatted results
Example Usage
"Calculate key financial ratios for this company based on the attached financial statements"
"What's the P/E ratio if the stock price is $50 and annual earnings are $2.50 per share?"
"Analyze the liquidity position using the balance sheet data"
Scripts
calculate_ratios.py: Main calculation engine for all financial ratiosinterpret_ratios.py: Provides interpretation and benchmarking
Best Practices
- Always validate data completeness before calculations
- Handle missing values appropriately (use industry averages or exclude)
- Consider industry context when interpreting ratios
- Include period comparisons for trend analysis
- Flag unusual or concerning ratios
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.
- 3d ago First seen · 70 lines · 23 tokens per session scan A 75b9aeac304a
analyzing-financial-statements is a skill published in the GitHub repository thevibeworks/claude-code-docs (38 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 506 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to analyzing-financial-statements, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
sec-plain-english
Draft, rewrite, or audit investor-facing financial and legal disclosure using an independently expressed interpretation of official SEC plain-English guidance. Use for prospectus summaries, risk factors, shareholder letters, offering materials, and securities disclosures that must be easier to understand without…
metatradermcp
Use when working with MQL4, MQL5, MetaTrader 4/5, Expert Advisors (EAs), custom indicators, or scripts. Covers OrderSend, iMACD, iRSI, CopyBuffer, trade operations, indicator buffers, and MQL4-to-MQL5 migration. Triggers on any .mq4/.mq5/.mqh file or MetaEditor compilation.
量化交易分析师工作流程（纪衡）
Skill "量化交易分析师工作流程（纪衡）" from CavinHuang/lume, covering 量化交易分析师 sop, 核心原则, 分析 sop, step 0：确认数据 and step 1：数据准备.
vobiz-partner-api
Vobiz Partner / reseller API - create customer sub-accounts, transfer balance, run KYC sessions (PAN+Aadhaar OTP, no documents), and query per-customer CDRs/transactions/numbers.
accounts-receivable-advanced
This skill should be used when AR runs as a dedicated standalone invoicing application rather than as a sub-module inside a books app — typically a US mid-market company that needs branded invoice templates, recurring billing, structured dunning, dispute management, credit holds, and a formal write-off workflow. The…
accounts-payable
This skill should be used when paying vendor bills at an organization under 100 employees — typically one person handling AP in QuickBooks, Xero, or a bill-pay tool like Bill.com or Ramp, with lightweight approvals and no formal purchase orders.