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/earnings)<a href="https://agentmods.dev/commands/godisego/hot-money/earnings"><img src="https://agentmods.dev/badge/commands/godisego/hot-money/earnings/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/earnings"><img src="https://agentmods.dev/badge/commands/godisego/hot-money/earnings.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.00022 | $0.00359 |
| Opus 5 | $0.00011 | $0.00179 |
| Sonnet 5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
earnings 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 10d 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 earnings — 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
/earnings <股票代码>
最新季报 beat/miss 快速解读。
工作流
- 采集财务历史
- 调用：
from lib.research_workflow import build_earnings_analysis result = build_earnings_analysis(features, raw, consensus={"rev": ..., "ni": ...})
输出
- Headline：双超预期 / 双不及 / 分化
- 最新季度：营收、净利、YoY%
- vs 共识：差异 %（+5% 大超 / +2% 小超 / ±2% 符合 / -2% 小不及 / -5% 大不及）
- 投资逻辑影响：
- 💪 强化看多（双 +5% 以上）
- ⚠️ 削弱看多
- ⚪ 保持观点
展示示例
Headline: 双超预期 — 营收 +3.2% / 净利 +5.8%
最新季度：
营收 12.5 亿 (YoY +18.5%) · vs 共识 12.1 亿 · 🟢 小幅超预期 (+3.3%)
净利 1.6 亿 (YoY +22.1%) · vs 共识 1.51 亿 · 🟢 小幅超预期 (+5.9%)
投资逻辑：💪 强化看多
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.
- 10d ago First seen · 40 lines · 22 tokens per session scan A cdc4b2adc7f5
earnings is a command published in the GitHub repository godisego/hot-money (2 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 359 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to earnings, 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…