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 Haochenhust/ch-skills --skill catalyst-trackergit clone --depth 1 https://github.com/Haochenhust/ch-skillsWrote 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/haochenhust/ch-skills/catalyst-tracker)<a href="https://agentmods.dev/skills/haochenhust/ch-skills/catalyst-tracker"><img src="https://agentmods.dev/badge/skills/haochenhust/ch-skills/catalyst-tracker/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/haochenhust/ch-skills/catalyst-tracker"><img src="https://agentmods.dev/badge/skills/haochenhust/ch-skills/catalyst-tracker.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.00072 | $0.00499 |
| Opus 5.5 | $0.00029 | $0.00200 |
| Sonnet 5.5 | $0.00014 | $0.00100 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
catalyst-tracker 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 2mo 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.
What it actually says
Catalyst Tracker
Maintains a forward-looking calendar of events that could trigger stock re-pricing.
When to Use
- During daily research — check what catalysts are approaching
- When building a trade thesis — identify timing
- Periodic self-check — review if the catalyst calendar is up to date
Catalyst Types
- Company-specific: Earnings reports, product launches, customer wins, management changes
- Industry events: Conferences (GTC, CES, MWC), trade shows, industry data releases
- Policy/Regulatory: Government policy announcements, regulatory changes
- Macro: Interest rate decisions, economic data releases, market sentiment shifts
Catalyst File
Maintain a consolidated calendar in catalysts-calendar.md (in your research notes directory). If you keep a per-stock research-state file, also note each stock's upcoming catalysts there.
# 催化剂日历
## 本周 ({date range})
- {date}: {event} → 影响标的: {stocks} | 预期影响: {brief}
## 下周
- ...
## 本月后续
- ...
## 远期 (1-3个月)
- ...
Workflow
Daily Check (part of a morning routine)
- Read catalysts-calendar.md
- Flag any catalyst happening today or tomorrow
- Surface it in your morning briefing / trade planning
Weekly Update
- Search for new upcoming events via WebSearch
- Remove passed catalysts
- Add newly discovered catalysts
- Link each catalyst to the affected stocks in your notes
Rules
- Every catalyst must have a specific date (or at least month/quarter)
- Every catalyst must link to at least one stock — unlinked events are noise
- Assess probability and impact — not all catalysts are equal
- Remove passed catalysts promptly — stale calendars are worse than no calendar
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.
- 2mo ago First seen · 63 lines · 72 tokens per session scan A 752ca91487a7
catalyst-tracker is a skill published in the GitHub repository Haochenhust/ch-skills (9 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 499 once invoked, about $0.0003 per session on Opus 5.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.
catalyst-tracker compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| catalyst-trackerHaochenhust/ch-skills | Skill | 9 | 3mo ago | MIT | A | 72 | Claude Code, Codex |
| rugpull-detectorDjordjeMojsilovic/Djordjes-Claude-Setup | Skill | 4 | 3mo ago | none | A | 205 | Claude Code, Codex |
| ma-playbookalirezarezvani/claude-skills | Skill | 29k | yesterday | MIT | A | 29 | Claude Code |
| fiscalisteromainsimon/paperasse | Skill | 2.6k | yesterday | MIT | A | 320 | Claude Code, Codex |
| comptableromainsimon/paperasse | Skill | 2.6k | yesterday | MIT | A | 153 | Claude Code, Codex |
| syndicromainsimon/paperasse | Skill | 2.6k | yesterday | MIT | A | 204 | Claude Code, Codex |
| prompt-masternidhinjs/prompt-master | Skill | 16k | 15d ago | MIT | B | 78 | Claude Code, Codex |