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 johnsonhk88/AI-Bank-Statement-Document-Automation-By-LLM-And-Personal-Finanical-Analysis-Prediction --skill bank-statement-parsinggit clone --depth 1 https://github.com/johnsonhk88/AI-Bank-Statement-Document-Automation-By-LLM-And-Personal-Finanical-Analysis-PredictionWrote 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/johnsonhk88/ai-bank-statement-document-automation-by-llm-and-personal-finanical-analysis-prediction/bank-statement-parsing)<a href="https://agentmods.dev/skills/johnsonhk88/ai-bank-statement-document-automation-by-llm-and-personal-finanical-analysis-prediction/bank-statement-parsing"><img src="https://agentmods.dev/badge/skills/johnsonhk88/ai-bank-statement-document-automation-by-llm-and-personal-finanical-analysis-prediction/bank-statement-parsing/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/johnsonhk88/ai-bank-statement-document-automation-by-llm-and-personal-finanical-analysis-prediction/bank-statement-parsing"><img src="https://agentmods.dev/badge/skills/johnsonhk88/ai-bank-statement-document-automation-by-llm-and-personal-finanical-analysis-prediction/bank-statement-parsing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.00209 |
| Opus 5 | $0.00012 | $0.00105 |
| Sonnet 5 | $0.00005 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
bank-statement-parsing 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.
What it actually says
Bank Statement Parsing Skill
Core Rules
- Always start by calling the
PDF Extractortool. - Do not trust "Paid In" / "Paid Out" column headers when they are ambiguous.
- Verify every transaction by checking how the running Balance changes:
- If Balance increases → Credit (Paid In)
- If Balance decreases → Debit (Paid Out)
- Extract Opening Balance from "Balance Brought Forward".
- Extract Closing Balance from the final running balance in the transactions.
- Preserve original descriptions exactly. Do not summarize or shorten them.
- If column alignment in the extracted text is messy, rely on balance math rather than position.
Expected Output
Return transactions in a consistent structure with: Date, Description, Debit, Credit, Balance.
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.
- 12d ago First seen · 21 lines · 23 tokens per session scan A 81134a9e57c6
bank-statement-parsing is a skill published in the GitHub repository johnsonhk88/AI-Bank-Statement-Document-Automation-By-LLM-And-Personal-Finanical-Analysis-Prediction (627 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 209 once invoked, about $0.0001 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 skills, from other repositories
report-generator
Generate professional HTML/PDF investment reports with interactive visualizations.
receipts-to-expenses
Read a batch of receipt images directly via vision, classify each into expense categories, optionally reconcile against a bank statement CSV, and produce a multi-sheet Excel workbook + a PDF summary. Use when given receipt photos and asked for an expense report.
financial-expense-automation
An expense-receipt workflow that reads PDF and image attachments, extracts their details, checks whether they are valid expense receipts, and records them in Feishu Bitable, a cloud table service.
pdf-invoice-extractor
OCR a PDF invoice with mistralocr and extract structured line-item data (vendor, date, amounts, VAT) for accounting reconciliation. Use when the user provides an invoice PDF to process.
deepread-bank-statements
Extract structured data from bank statements — account holder, period, opening/closing balances, and every transaction as typed JSON. Works on PDF and scanned statements from any bank. Per-field confidence flags. PII redaction for compliant sharing. Free 2,000 pages/month.
deepread-purchase-orders
Extract structured data from purchase orders — PO number, buyer/supplier, line items, quantities, prices, delivery dates, totals — as typed JSON. 2-way/3-way match against invoices. Per-field confidence flags. Free 2,000 pages/month.