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.
git clone --depth 1 https://github.com/godisego/hot-moneyWrote 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/commands/godisego/hot-money/lbo)<a href="https://agentmods.dev/commands/godisego/hot-money/lbo"><img src="https://agentmods.dev/badge/commands/godisego/hot-money/lbo/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/commands/godisego/hot-money/lbo"><img src="https://agentmods.dev/badge/commands/godisego/hot-money/lbo.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.00031 | $0.00402 |
| Opus 5 | $0.00015 | $0.00201 |
| Sonnet 5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
lbo 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 9d 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 lbo — 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.
What it actually says
/lbo <股票代码>
作为估值交叉验证，测试"如果 PE 基金今天按市场价买入并 5 年后退出，能否赚到 20%+ IRR？"
工作流
from lib.fin_models import quick_lbo
result = quick_lbo(features,
entry_multiple=8.0, # 入场 EV/EBITDA
debt_multiple=5.0, # 杠杆倍数 (5x EBITDA)
exit_multiple=8.0, # 退出 EV/EBITDA
hold_years=5,
ebitda_growth=0.08, # 年化 EBITDA 增速
interest_rate=0.06,
)
输出
- 入场：EBITDA × 8x → EV → 债务 (5x) + 股权
- 5 年 EBITDA 路径
- 债务偿还进度：FCF × 70% 还债
- 退出：Y5 EBITDA × 8x → EV - 剩余债 = 股权
- IRR / MOIC
- verdict：
- 🟢 IRR ≥ 20% — PE 可赚
- 🟡 15-20% — 边际
- 🔴 < 15% — PE 不会买
为什么重要
LBO 测试是"私募买方视角的估值下限"。如果一个股票连 PE 基金用杠杆都赚不到钱，说明市场定价已经很贵了。这是对 DCF 的独立交叉校验。
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.
- 9d ago First seen · 39 lines · 31 tokens per session scan A 72081d8f2a7c
lbo is a command published in the GitHub repository godisego/hot-money (2 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 402 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to lbo, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…