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 agentmods add skills/skloxo/tidetrading/execution-modelnpx skills add skloxo/TideTrading --skill execution-modelgit clone --depth 1 https://github.com/skloxo/TideTradingWhat 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 | $0.00041 | $0.02984 |
| Opus 5 | $0.00020 | $0.01492 |
| Sonnet 5 | $0.00008 | $0.00597 |
| Haiku 4.5 | $0.00004 | $0.00298 |
Grade A, and why
execution-model 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trade Execution Modeling
Overview
Provide more realistic execution assumptions for backtests, including slippage models, market-impact estimation, and execution-algorithm principles. This skill is for backtest simulation only and does not involve live order execution.
Slippage Models
Why Slippage Models Are Needed
Idealized backtest: filled at the close, zero slippage
Real world:
1. The order book has a bid-ask spread
2. Large orders push prices (market impact)
3. Execution is delayed (there is latency from signal to fill)
No slippage model -> overly optimistic backtest -> losses in live trading
1. Fixed Slippage Model
def fixed_slippage(price: float, direction: int, bps: float = 5.0) -> float:
"""
Args:
price: Original price
direction: 1=buy, -1=sell
bps: Slippage in basis points (1bp = 0.01%), default 5bp
Returns:
Execution price after slippage
"""
slippage = price * bps / 10000
return price + direction * slippage
Reference fixed-slippage assumptions by market:
| Market | Instrument | Suggested Slippage (bps) | Notes |
|---|---|---|---|
| China A-share large cap | CSI 300 constituents | 3-5 | Good liquidity |
| China A-share small cap | CSI 1000 constituents | 5-10 | Average liquidity |
| China micro-cap | market cap < 5 billion RMB | 10-30 | Poor liquidity |
| US large cap | AAPL / MSFT | 1-3 | Excellent liquidity |
| Hong Kong stocks | Hang Seng constituents | 5-10 | Less liquid than A / US |
| BTC spot | BTC-USDT | 2-5 | Good OKX liquidity |
| ETH spot | ETH-USDT | 3-8 | Slightly worse than BTC |
| Small altcoins | other -USDT pairs |
10-50 | Liquidity varies widely |
2. Linear Impact Model
def linear_impact(price: float, direction: int,
volume_traded: float, adv: float,
impact_coeff: float = 0.1) -> float:
"""
Linear market impact: impact ∝ traded volume / ADV
Args:
price: Original price
direction: 1=buy, -1=sell
volume_traded: Trade size (shares or notional)
adv: Average Daily Volume
impact_coeff: Impact coefficient, usually 0.05-0.2
Returns:
Execution price after impact
"""
participation_rate = volume_traded / adv
impact = impact_coeff * participation_rate
return price * (1 + direction * impact)
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.
- 3d ago First seen · 350 lines · 41 tokens per session scan A 1d42ba51319d
execution-model is a skill published in the GitHub repository skloxo/TideTrading (10 stars, last pushed 9d ago), licensed MIT. It adds 41 tokens to every session and 2,984 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-31.
Other skills, from other repositories
daily-deep-brief
8 点这个时点：HK 开盘前 90 分钟，US 已收盘 4 小时。盘前是 deep think 最好的窗口 — 有完整夜间消息面，没有盘中执行压力。.
hk-stock-analysis
Workspace-aware Hong Kong stock analysis for kcn. Routes through clawock analyze-hk (Tencent primary + Eastmoney full-batch independent cross-check/fallback → stooq → yfinance) for price/技术指标/news, layered with HK-specific concepts — 南向资金, HSTECH 方向, 杠杆 ETF 衰减, 老千股警惕, T+0 无涨跌幅. Use when user asks about a HK ticker…
us-stock-analysis
Workspace-aware US stock analysis for kcn. Routes through clawock analyze-us / clawock us-quotes instead of generic web search, then layers fundamental/technical/news analysis on top. Use when user asks to analyze a US ticker (e.g. "analyze AAPL", "look at RKLB", "compare TSLA vs NVDA"), check earnings, run…
invest-analyst
全能证券分析师工作台——把零散金融工具串成机构级工作流。覆盖个股IC研报、主题策略、事件驱动（电话会/业绩/政策/并购）、一致预期整合、行业比较、市场日报五大场景。 触发：「出一份茅台的IC报告」「写一份XX的行业深度」「XX业绩电话会纪要」「怎么看待XX政策/并购」「这个产业链有哪些标的」「分析师一致预期」「今天市场怎么样」「出个日报晨报」「这个投资论点怎么写」。 与invest系列区别：invest-stock/fund做「买不买」的判断，invest-analyst做「怎么写/怎么产出」的机构级内容交付。invest-industry做「行业是什么」，invest-analyst做「这个行业怎么投」。.
invest-fund
场景优先级：B(同经理) > F(跨基金对比) > G(行业) > C(次新) > E(ETF) > A(默认).
invest-stock
Skill "invest-stock" from taxueseek/fund-investment-guide, covering invest-stock：统一个股分析, 模式自动选择, 快速识别, 模式 1：三关审查（默认，a股/港股） and 哲学锚点.