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/catalysts)<a href="https://agentmods.dev/commands/godisego/hot-money/catalysts"><img src="https://agentmods.dev/badge/commands/godisego/hot-money/catalysts/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/catalysts"><img src="https://agentmods.dev/badge/commands/godisego/hot-money/catalysts.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.00028 | $0.00323 |
| Opus 5 | $0.00014 | $0.00161 |
| Sonnet 5 | $0.00006 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
catalysts 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 catalysts — 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
/catalysts <股票代码>
工作流
- 从 dim 15 (事件驱动) 提取历史事件 + 预排标准日程
- 调用：
from lib.research_workflow import build_catalyst_calendar cal = build_catalyst_calendar(features, raw)
输出
- 已发生事件（按时间倒序，分类打标 high/medium/low）
- 未来 30 天：
- 季报披露窗口（高影响）
- 股东大会 / 投资者关系活动（中影响）
- 未来 60 天：
- 行业展会 / 新品发布（中影响）
- 宏观节点：
- 美联储 FOMC 会议（参考）
- 统计：
high_impact_count,next_30d列表
展示样式
2026-04-30 [HIGH] 2026 Q1 季报披露（关注营收/净利超预期与否）
2026-05-15 [MED] 股东大会
2026-06-15 [MED] 行业展会
2026-05-28 [LOW] 美联储 FOMC (参考)
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 · 37 lines · 28 tokens per session scan A e01f33d217bc
catalysts is a command published in the GitHub repository godisego/hot-money (2 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 323 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 catalysts, 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…