event-driven

event-driven is a skill for Claude Code, Codex from HKUDS/Vibe-Trading. It costs 38 tokens per session (2,086 once invoked), scanned A, original, MIT.

An event-based trading strategy that turns news, announcements, and economic-policy events into sentiment scores from bearish to bullish. The events are stored in a CSV file, then combined with technical signals using time decay and weighted aggregation.

In plain words
What is it for?
Use it to record earnings news, policy changes, and macroeconomic announcements, score their likely market effect, and combine those scores with technical signals in a strategy.
Why use it?
It separates the event data from the trading logic, making the source information easier to inspect and update. It also provides a consistent format for combining news interpretation with price-based analysis.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to record earnings news, policy changes, and macroeconomic announcements, score their likely market effect, and combine those scores with technical signals in a strategy.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hkuds/vibe-trading/event-driven
About the project

Vibe-Trading is a personal trading agent that gives an AI system tools for market analysis, algorithmic trading, backtesting, and related workflows. It is for users who want an agent to research and evaluate trading strategies or manage simulated and other trading activities. The catalogue contains skills that expose these trading capabilities to compatible agents.

HKUDS/Vibe-Trading · 33,017 stars · on GitHub · vibetrading.wiki

Install

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.

Any agent
npx skills add HKUDS/Vibe-Trading --skill event-driven
Clone the repo
git clone --depth 1 https://github.com/HKUDS/Vibe-Trading

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for event-driven

README.md
[![agentmods](https://agentmods.dev/badge/skills/hkuds/vibe-trading/event-driven/github.svg)](https://agentmods.dev/skills/hkuds/vibe-trading/event-driven)
Your own site
<a href="https://agentmods.dev/skills/hkuds/vibe-trading/event-driven"><img src="https://agentmods.dev/badge/skills/hkuds/vibe-trading/event-driven/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.

agentmods 80×15 button for event-driven

Your own site · 80×15
<a href="https://agentmods.dev/skills/hkuds/vibe-trading/event-driven"><img src="https://agentmods.dev/badge/skills/hkuds/vibe-trading/event-driven.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,086 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Fable 5.1 · 6 Sept 2026 📄 Read the review Third-party audits
  • Snyk warn 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.02086
Opus 5 $0.00019 $0.01043
Sonnet 5 $0.00008 $0.00417
Haiku 4.5 $0.00004 $0.00209

Measured 9d ago against content hash 169e5bfab7e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

event-driven 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.

The scan reads SKILL.md. This mod also ships 1 executable file (example_signal_engine.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agent/src/skills/event-driven/SKILL.md · 181 lines

How it starts

The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Event-Driven Strategy

Purpose

Uses event information such as news, announcements, and macro policy updates. The LLM analyzes sentiment and impact magnitude to generate event-driven trading signals. Event data is managed in CSV format, and technical signals are combined with event signals through weighted aggregation to form the final trading decision.

Workflow

  1. Data collection: use the read_url tool to fetch the full text of news and announcements
  2. LLM analysis: the LLM reads the news and scores it from -1.0 to 1.0 with a standardized prompt (extremely bearish to extremely bullish)
  3. Generate the event CSV: write data in the date,event_type,score,source,summary schema
  4. Signal aggregation: signal_engine.py reads the event CSV, applies time decay, and combines it with the technical signal

Key principle: the event CSV is the data layer, and signal_engine.py is the logic layer. Keep them decoupled.

Event CSV Schema

date,event_type,score,source,summary
2024-01-15,earnings,0.8,read_url,Q4 revenue beat expectations by 30%
2024-01-20,macro,-0.5,read_url,Central bank raised rates by 25bp
2024-02-01,policy,0.3,read_url,New-energy subsidies extended
2024-02-10,sentiment,-0.7,read_url,Bearish sentiment surged on social media
2024-03-05,insider,0.4,read_url,CEO bought 5 million shares

Field descriptions:

Field Type Description
date str (YYYY-MM-DD) Date when the event became knowable (publication date, not occurrence date. If released after market close → use the next trading day)
event_type str earnings / macro / policy / sentiment / insider / technical_break
score float -1.0 ~ 1.0 (standardized LLM score)
source str Data-source tag (such as read_url)
summary str Event summary (one sentence, no commas)

Event Type Details

Type Meaning Typical Impact Duration
earnings Earnings release Short-term shock 1-5 days
macro Macro data / central-bank policy Medium-term impact 5-20 days
policy Industry policy / regulatory change Long-term impact 20-60 days
sentiment Market sentiment / public opinion Short-term shock 1-3 days
insider Insider trading / block trade Medium-term signal 5-10 days
technical_break Break of a key technical level Short-term catalyst 1-5 days

Read the full file on GitHub · 181 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 9d ago First seen · 181 lines · 38 tokens per session scan A 169e5bfab7e8

Subscribe to this mod's changes

event-driven is a skill published in the GitHub repository HKUDS/Vibe-Trading (33,017 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 2,086 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

hyperliquid

Use when backtesting, deploying, checking funding readiness, or debugging a Hyperliquid strategy through Superior Trade Unified API — writing Freqtrade configs and strategy code, running sweeps, checking managed-wallet balances, trading HIP-3 perps, or diagnosing a deployment that will not start or trade.

Superior-Trade/superior-skills · 64 tokens

polymarket

Use when the user wants to trade, research, or backtest Polymarket prediction markets through Superior Trade — finding markets by slug or event URL, placing a single immediate market order, writing NautilusTrader strategies, running filled-data backtests, funding pUSD, or deploying and monitoring a live Polymarket…

Superior-Trade/superior-skills · 68 tokens

aerodrome

Use when creating, validating, backtesting, deploying, sizing, or troubleshooting Aerodrome/Base spot trading strategies through the Superior Trade API, especially Freqtrade configs using exchange.name "aerodrome", AERO/USDC or CHECK/USDC pairs, AMM market swaps, wallet/gas balance checks, no-orderbook pricing, or…

Superior-Trade/superior-skills · 83 tokens

backtesting

Use when running, interpreting, or designing backtests on Superior Trade — anything about backtest windows, trade-count thresholds, exit-reason mix, parameter sweeps, walk-forward validation, zero-trade diagnosis, compute-cost estimation, or "is this backtest result trustworthy?". Pair with the relevant strategy…

Superior-Trade/superior-skills · 73 tokens

basis-arb

Use when the user asks for spot-perp basis trade, basis arbitrage, cash-and-carry, perp discount, or any setup that reads the spot–perp basis as a positioning signal. Long-perp leg only — pure two-leg basis arb requires a paired spot short (or long) which Freqtrade can't run cleanly. The strategy below captures the…

Superior-Trade/superior-skills · 87 tokens

fees-optimizations

Use when the user asks about fees, fee optimization, slippage, maker vs taker, post-only or ALO orders, fee tiers, builder code fees, effective spread, order pricing, lowering trading costs, or why a live Hyperliquid Freqtrade strategy underperforms its backtest. Also use proactively for high-turnover designs (5m or…

Superior-Trade/superior-skills · 94 tokens