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.
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 HKUDS/Vibe-Trading --skill research-goalgit clone --depth 1 https://github.com/HKUDS/Vibe-TradingWrote 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/hkuds/vibe-trading/research-goal)<a href="https://agentmods.dev/skills/hkuds/vibe-trading/research-goal"><img src="https://agentmods.dev/badge/skills/hkuds/vibe-trading/research-goal/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/hkuds/vibe-trading/research-goal"><img src="https://agentmods.dev/badge/skills/hkuds/vibe-trading/research-goal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00618 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
research-goal 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 8d 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:
- research-goal — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal-Driven Finance Research
Use this skill when a user asks for a multi-step finance research task, comparison, audit, thesis review, or "keep working until the answer is supported." The goal runtime is for research only. Never use it to place, submit, or execute trades.
When to Attach a Goal
Start a goal when the task has any of these traits:
- It needs multiple criteria before a conclusion is credible.
- It compares strategies, assets, regimes, or evidence sources.
- It may continue across turns or require a final audit.
- The user asks for "long driven task", "goal", "审计", "对比", "研究结论", or similar.
Do not start a goal for a tiny one-shot answer unless the user explicitly asks.
Tool Flow
- Call
start_research_goalwith a concise research-only objective. - Include 3-5 acceptance criteria when the user provided enough context.
- Before continuing an existing task, call
get_research_goal. - After a market-data lookup, backtest, document read, web source, or manual reasoning step, call
add_goal_evidence. - Link evidence to a criterion using
criterion_idorcriterion_index. - When all required criteria have been audited, call
update_research_goal_status.
Criteria Template
Use this shape when the user did not provide criteria:
- Define the research-only thesis and symbol universe.
- Collect fresh market, benchmark, or artifact evidence.
- Compare alternatives or a control baseline.
- Record caveats, contradictions, and the non-advice boundary.
Evidence Rules
- Keep evidence short and concrete.
- Prefer artifact-backed evidence when a tool produced a run or file.
- Include
run_id,artifact_path,source_provider,source_type,symbol_universe,benchmark, anddata_as_ofwhen known. tool_call_idis traceability only. Completion needs verified evidence from an existingrun_idor an allowedartifact_pathwith a matching sha256 hash.- Do not mark live trading instructions as evidence. Refuse or reframe them as research-only analysis.
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.
- 8d ago First seen · 58 lines · 0 tokens per session scan A eeaf0bb21cbf
research-goal is a skill published in the GitHub repository HKUDS/Vibe-Trading (33,177 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 618 tokens. 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-09-03.
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.
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…
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…
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…
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…
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…