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 8vdx1/fundos-mcp --skill fundos-lp-reportinggit clone --depth 1 https://github.com/8vdx1/fundos-mcpWrote 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/8vdx1/fundos-mcp/fundos-lp-reporting)<a href="https://agentmods.dev/skills/8vdx1/fundos-mcp/fundos-lp-reporting"><img src="https://agentmods.dev/badge/skills/8vdx1/fundos-mcp/fundos-lp-reporting/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/8vdx1/fundos-mcp/fundos-lp-reporting"><img src="https://agentmods.dev/badge/skills/8vdx1/fundos-mcp/fundos-lp-reporting.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.01368 |
| Opus 5 | $0.00051 | $0.00684 |
| Sonnet 5 | $0.00020 | $0.00274 |
| Haiku 4.5 | $0.00010 | $0.00137 |
Grade A, and why
fundos-lp-reporting 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LP Communications
Three principles, in priority order.
Accuracy over elegance. A polished letter with a wrong distribution figure destroys more credibility than a plain one ever built. Numbers tie to the books; dates are exact.
Transparency over spin. LPs have read every flavour of rose-tinted update. A write-down disclosed promptly and plainly builds more trust than a strong quarter padded with qualifications. Bad news does not improve with age.
Calibrate to the reader. A pension fund expects formal structure and full ILPA detail. A family office often prefers a warmer, shorter note. Same facts, different register.
Draft only. Never send.
You have no path to an LP inbox and must not construct one. Produce the draft, hand it to the GP, and say explicitly that it has not been sent. This holds for every communication type below without exception.
Ground the letter in real data
Never write an LP update from remembered numbers.
fundos GET /fundos/investors/lp # roster, commitments, KYC
fundos GET /fundos/investors/lp/12 # one LP: capital account + ledger
fundos GET /fundos/investors/lp/12/memory # relationship brief — read before drafting
fundos GET /fundos/cfo/accounts # fund-level NAV
fundos GET /fundos/crm/pipeline # portfolio and stages
fundos GET /fundos/transactions # recent closings and exits
fundos POST /fundos/cfo/report '{"fund_account_id": 3, "start": "2026-01-01", "end": "2026-03-31"}'
/memory returns the LP's living brief — engagement read, confirmed asks, prior
commitments. Read it before drafting anything addressed to that LP. It is what stops you
re-asking a question they answered last quarter, or ignoring a concern they raised. Note it
deliberately excludes MNPI.
Communication types
Quarterly report — within 90 days of quarter end
Performance metrics (DPI, RVPI, TVPI, net IRR) against the prior period; portfolio company summaries covering progress and concerns; per-LP capital account statement; notable events; optional market commentary. Typically 4–8 pages, performance summary first, financials attached separately.
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 · 116 lines · 102 tokens per session scan A 80dfc575166e
fundos-lp-reporting is a skill published in the GitHub repository 8vdx1/fundos-mcp (1 stars, last pushed 27d ago), licensed MIT. It adds 102 tokens to every session and 1,368 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
fintech-campaign-designer
Design full fintech campaigns from concept to execution — promotion strategy, mechanic, user journey, budget, and risk assessment. Use when the user needs end-to-end campaign design for a fintech/payments/lending platform. Specialized for SEA markets (Vietnam, Indonesia, Philippines, Thailand).
dcf-model
Build discounted cash flow valuation workbooks in Excel.
comps-analysis
Build comparable-company valuation workbooks in Excel.
stocks
Stock quotes, history, search, compare, crypto via Yahoo.
polymarket
Query Polymarket: markets, prices, orderbooks, history.
connect-recommend
Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue…