UZI-Skill is a collection of coding-agent skills for analyzing individual stocks across Chinese, Hong Kong, and United States markets using public data, investor viewpoints, quantitative rules, and institutional analysis methods. It is for users who want an agent to produce detailed stock-analysis reports. The catalogue entries are the commands, skills, instructions, plugin, agent, and hook that provide this workflow in supported coding agents.
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/wbh604/UZI-SkillWrote 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/wbh604/uzi-skill/catalysts)<a href="https://agentmods.dev/commands/wbh604/uzi-skill/catalysts"><img src="https://agentmods.dev/badge/commands/wbh604/uzi-skill/catalysts.svg" alt="Measured on agentmods" 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- catalysts — 100% identical, 0 lines differ
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.
- 7d ago First seen · 37 lines · 28 tokens per session scan A e01f33d217bc
catalysts is a command published in the GitHub repository wbh604/UZI-Skill (6,781 stars, last pushed 2d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
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…
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.