Skip to content

Repository files navigation

LibreFinTech Claude Code

LibreFinTech Claude Code

Financial technology development with Claude Code — 20 specialized plugins for payments, ledgers, trading, compliance, and risk

Stars License Last Commit FinTech Claude Code


Skills, agents, commands, and workflows for shipping financial technology with Claude Code.

FinTech is where wrong code costs real money. A payment processor that double-charges. A ledger that loses a cent in rounding. A fraud system that approves the wrong transaction. Generic LLM coding patterns don't have the domain awareness to catch these. LibreFinTech gives Claude Code the financial-specific expertise needed to ship systems that handle money correctly.

Twenty domain plugins. Three flagship areas depth-complete (payment processing, ledger design, fraud detection). 3-tier learning paths covering compliance, security, and operational reality. The substance you'd expect from a senior fintech engineer.


The shift this kit responds to

Karpathy, December 2025:

"I've never felt this much behind as a programmer. The profession is being dramatically refactored."

For fintech specifically, the refactor is harder than other domains. AI codegen that produces a working webapp can produce a payment system that "works" but silently drops 0.01% of transactions. The cost of wrong is high; the time to discover wrong can be months. LibreFinTech encodes the patterns that catch these defects at design time.

Where LibreFinTech fits in the Claude Code stack

Claude Code component LibreFinTech provides
Plugins 20 fintech subdomain plugins (payments, ledger, trading, compliance, risk, fraud, more)
Agents Specialist agents per plugin (payment engineer, ledger architect, fraud analyst)
Commands Quick-access slash commands per plugin
Skills Pattern libraries (idempotency keys, double-entry invariants, fraud rules)
Templates Webhook handlers, ledger schemas, compliance report scaffolds

The 20 plugins

Money movement

Plugin Agent / Command What it covers
payment-processing ⭐ /payments Stripe + Adyen + native rails, 3DS, idempotency keys, webhook reliability, refund + chargeback flows, payment retries
real-time-settlement /settlement RTGS, instant payments (FedNow, SEPA Instant, Faster Payments), clearing, netting
open-banking /open-banking PSD2 + Open Banking Standard, consent flows, account aggregation, AISP/PISP roles
banking-apis /banking-api Direct bank integrations, ACH, wire transfers, ledger sync

Accounting + ledgers

Plugin Agent / Command What it covers
ledger-design ⭐ /ledger Double-entry bookkeeping, balance invariants, event sourcing, immutability, multi-currency, rounding
reconciliation /reconcile Transaction matching, exception handling, bank statement parsing, settlement reconciliation
financial-reporting /fin-report GAAP / IFRS reporting, trial balance, P&L + balance sheet generation, audit packages
audit-trails /audit-trail Immutable audit logs, event sourcing, compliance trails, chain-of-custody

Risk + fraud

Plugin Agent / Command What it covers
fraud-detection ⭐ /fraud-detect Rule engines, ML scoring, anomaly detection, velocity checks, device fingerprinting, dispute defense
risk-management /risk Market / credit / operational risk, VaR, stress testing, capital adequacy
regulatory-compliance /compliance SOX, MiFID II, Dodd-Frank, GDPR for financial data, regulatory reporting cadences
kyc-aml /kyc-aml Identity verification (KYC), sanctions screening (OFAC, EU), ongoing monitoring, transaction monitoring (AML)
financial-security /fin-security PCI DSS scope minimization, encryption at rest + in transit, tokenization, key management, HSM patterns

Trading + markets

Plugin Agent / Command What it covers
trading-systems /trading Order management, matching engines, FIX protocol, market connectivity, smart order routing
market-data /market-data Real-time + historical market data, tick data, OHLCV normalization, exchange feeds
portfolio-management /portfolio Portfolio construction, rebalancing, allocation strategies, performance attribution
pricing-engines /pricing Dynamic pricing, fee calculation, interest computation, FX rates, yield curves

Specialized verticals

Plugin Agent / Command What it covers
lending-platforms /lending Loan origination, credit scoring, underwriting, servicing, collections
insurance-tech /insurtech Claims processing, underwriting automation, policy management, actuarial models
cryptocurrency /crypto Wallet management, smart contracts, DeFi protocols, custody patterns, chain analysis

⭐ = depth-complete plugins (substantive expert content). The other 17 are shell-improved (better than templates, deeper in v0.3).

Each plugin ships one agent, one slash command, and one skill: 20 agents, 20 commands, and 20 skills in all. An optional 21st plugin, libre-fintech-hooks, adds safety and context hooks (see below).


Quick start

Install from Claude Code

/plugin marketplace add HermeticOrmus/LibreFinTech-Claude-Code
/plugin install payment-processing@libre-fintech

Install any other plugin the same way, by the name in the tables above: /plugin install <plugin>@libre-fintech. From a terminal, the same thing is:

claude plugin marketplace add HermeticOrmus/LibreFinTech-Claude-Code
claude plugin install payment-processing@libre-fintech

Install in Grok Build

Grok Build reads the same plugin folders. Add the marketplace, then install any plugin by the name in the tables above:

grok plugin marketplace add HermeticOrmus/LibreFinTech-Claude-Code
grok plugin install payment-processing@LibreFinTech-Claude-Code --trust

Grok asks you to trust a plugin before it installs it; --trust is that answer. To install one plugin straight from its folder, without the marketplace:

grok plugin install HermeticOrmus/LibreFinTech-Claude-Code#plugins/payment-processing --trust

From a clone, ./setup.sh --grok installs every plugin into Grok Build, with the same --only, --list, and --uninstall options. libre-fintech-hooks uses a hook format Grok Build supports, but it has not been verified in a live Grok session yet.

Install everything with setup.sh

setup.sh registers your clone as the libre-fintech marketplace and installs every plugin through the Claude Code CLI. ./setup.sh --list shows the plugins, ./setup.sh --only payment-processing,ledger-design,fraud-detection installs a subset, and ./setup.sh --uninstall removes them. It needs claude and jq on your PATH.

git clone https://github.com/HermeticOrmus/LibreFinTech-Claude-Code.git ~/projects/LibreFinTech-Claude-Code
cd ~/projects/LibreFinTech-Claude-Code
./setup.sh

Then in any Claude Code session at your fintech project root:

/payments design idempotent payment processing for a marketplace with split payouts, support for refunds + partial refunds, and 3DS challenge flow for EU customers

See QUICK_START.md for the full walkthrough (build a working payment flow with Stripe + idempotency in 30 minutes).

Optional hooks

/plugin install libre-fintech-hooks@libre-fintech

libre-fintech-hooks asks before Claude reads or writes .env files, private keys, keystores, credentials and secrets files, or anything under ledger-data/, transaction-dumps/, or pii-exports/, and before rm -rf, git push --force, git reset --hard, or SQL DROP, TRUNCATE, and DELETE FROM in a shell command. It also warns when a write leaves a file empty, reminds Claude once per session to run the tests after a code change, and notes detected ledger, payments, SDK, and compliance signals at session start. It needs jq. A full ./setup.sh run installs it; --only leaves it out unless you name it. Details: plugins/libre-fintech-hooks.


Learning paths

Beginner — "My first fintech feature"

You've shipped web apps. You're now building something that handles money. The beginner path covers the foundational mindset shifts: idempotency, double-entry, the difference between "transaction succeeded" and "money actually moved."

→ learning-paths/beginner.md

Intermediate — "Production fintech without the disasters"

Your fintech feature is live. Now you need to handle: chargebacks, fraud attempts, reconciliation, regulatory inquiries, multi-currency, FX, partial outages, settlement delays.

→ learning-paths/intermediate.md

Advanced — "Compliance, scale, and ops"

You operate at scale. Now: SOC 2, PCI DSS audit prep, multi-region settlement, custom risk models, regulatory reporting at multiple jurisdictions, live-ops for financial systems.

→ learning-paths/advanced.md


Compatibility

  • Languages covered: Python, TypeScript, Go, Rust, Java (for high-frequency contexts)
  • Payment providers covered deeply: Stripe, Adyen, PayPal, Square, native rails (ACH, SEPA, FedNow, Faster Payments)
  • Bank API providers: Plaid, Tink, TrueLayer, Belvo (LatAm), Mono (Africa)
  • Compliance frameworks: PCI DSS, SOC 2, ISO 27001, GDPR + CCPA, regional KYC/AML (US BSA, EU AMLD, UK MLR)
  • Skill level: experienced web developers entering fintech (most useful) through senior fintech engineers (still useful as a reference)

LibreFinTech makes no calls to external services from within the plugin content itself — the plugins are documentation + prompt-engineering, not runtime middleware.


Feedback

Starred this? Tell us what worked and what is missing: open a feedback issue. Every piece of feedback gets an answer, and changes that come from it are credited in the release notes.


Contribute


Contributing

FinTech is wide and jurisdiction-specific. PRs especially welcome for:

  • Regional patterns: SEA fintech (PayNow, GrabPay), LATAM fintech (PIX, Mercado Pago, Belvo), African fintech (M-Pesa, Mono, Flutterwave), Indian fintech (UPI, RBI compliance)
  • Vertical depth: insurtech is currently light; lending compliance varies wildly by jurisdiction
  • Compliance translations: this kit is US/EU-centric; non-Western regulatory regimes under-served
  • Real war stories: case studies of fintech systems that broke + how they were fixed (anonymized)
  • Crypto / DeFi depth: currently broad-strokes; deeper protocol-specific content welcome

See CONTRIBUTING.md.


Disclaimer

This is documentation and prompt-engineering tooling. It is not financial advice. It is not legal advice. It is not compliance certification.

Building fintech systems in regulated jurisdictions requires:

  • Licensed legal counsel
  • Compliance officer or compliance partner
  • Regulatory approval (most jurisdictions require some form)
  • Audit (SOC 2, PCI DSS, etc., as applicable)

This toolkit helps you build correctly; it does not absolve you of the regulatory + legal responsibility for what you ship.


Part of the Libre Open-Source Stack for Claude Code

This repository is part of a growing family of open-source toolkits for Claude Code.

Libre suite — comprehensive plugin bundles

Skills mini-repos — single CLAUDE.md drop-ins

Template source

Star the family, not just one — that's how the suite stays coherent.