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 JoelLewis/finance_skills --skill financial-planning-integrationgit clone --depth 1 https://github.com/JoelLewis/finance_skillsWrote 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/joellewis/finance_skills/financial-planning-integration)<a href="https://agentmods.dev/skills/joellewis/finance_skills/financial-planning-integration"><img src="https://agentmods.dev/badge/skills/joellewis/finance_skills/financial-planning-integration/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/joellewis/finance_skills/financial-planning-integration"><img src="https://agentmods.dev/badge/skills/joellewis/finance_skills/financial-planning-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Output Handling · line 157 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
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.00185 | $0.05140 |
| Opus 5 | $0.00093 | $0.02570 |
| Sonnet 5 | $0.00037 | $0.01028 |
| Haiku 4.5 | $0.00018 | $0.00514 |
Grade A, and why
financial-planning-integration 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Financial Planning Integration
Core Concepts
Financial Planning System Architecture
The financial planning engine is the analytical hub of the advisor technology stack. It ingests client data from multiple systems, models the client's financial future, and produces outputs that drive portfolio construction, cash management, and ongoing advisory recommendations. (For the planning methodology those engines implement, see financial-planning-workflow.)
Relationship to other systems in the advisor technology stack:
- CRM (client relationship management): Source of client demographic data, household composition, employment status, life events, and planning review triggers. The CRM is the system of record for client facts; the planning tool consumes these facts as inputs.
- PMS (portfolio management system): Source of current portfolio holdings, asset allocation, and account types. The plan produces a required return target and risk capacity that feed back to the PMS as constraints for portfolio construction.
- Custodian: Source of account balances, positions, and transaction history. Custodial data feeds ensure the plan reflects actual account values rather than stale estimates.
- Aggregation platform: Source of held-away assets — accounts at other custodians, employer retirement plans, bank accounts, real estate equity estimates, stock options. Aggregation fills the gap between what the advisor custodies and what the client actually owns, which is essential for a complete financial picture.
Common financial planning platforms (as of 2026; verify current vendor lineups): eMoney Advisor, MoneyGuidePro (Envestnet), RightCapital, Naviplan (InvestCloud), and planning modules embedded within all-in-one platforms (e.g., Orion Planning, Advyzon). Platform selection depends on firm size, integration requirements, planning complexity, and client-facing presentation needs. Some platforms emphasize interactive client portals (eMoney, RightCapital); others emphasize advisor-facing analytical depth (MoneyGuidePro, Naviplan).
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 · 187 lines · 185 tokens per session scan A 5570ade5586f
financial-planning-integration is a skill published in the GitHub repository JoelLewis/finance_skills (184 stars, last pushed 1mo ago), licensed MIT. It adds 185 tokens to every session and 5,140 once invoked, about $0.0009 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
multi-nif
Integrate BeeL's multi-NIF model: one account holding many companies (fiscal identities), targeting a specific company per request, members and grants, and managed accounts (agencies / gestorías / fleets that invoice on behalf of others). Use when the integration deals with several NIFs/CIFs under one API key, the…
upgrade
Bring an existing BeeL. integration up to date: read the release notes and changelog, find which of the project's own calls the breaking changes hit, and propose the diff. Use when asked whether a BeeL integration is current, to migrate off deprecated routes, after BeeL announces changes, or periodically as…
payuni-query
A tool for checking PAYUNi transaction records through its Query API. PAYUNi is a Taiwan payment gateway, and a transaction query asks the gateway for an order’s current payment result.
usage-based-billing
Guide for charging directly per measured API call, token, storage unit, or other consumption using meters, stable usage events, aggregation, free thresholds, and metered subscriptions.
visa-best-practices
Best practices and integration guide for Visa developer APIs and payment protocols — covers platform setup, authentication, encryption, and product-specific workflows. Trigger keywords: VDP, Visa Developer Platform, VIC, Visa Intelligent Commerce, MPP, Machine Payments Protocol, X-Pay Token, Two-Way SSL, Mutual TLS…
kryptogo-pay-query
An implementation guide for querying KryptoGO Payment, a stablecoin payment service, to check individual or multiple payment records.