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 BaggaT236/AI-Trading-Skills --skill edge-hint-extractorgit clone --depth 1 https://github.com/BaggaT236/AI-Trading-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/baggat236/ai-trading-skills/edge-hint-extractor)<a href="https://agentmods.dev/skills/baggat236/ai-trading-skills/edge-hint-extractor"><img src="https://agentmods.dev/badge/skills/baggat236/ai-trading-skills/edge-hint-extractor/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/baggat236/ai-trading-skills/edge-hint-extractor"><img src="https://agentmods.dev/badge/skills/baggat236/ai-trading-skills/edge-hint-extractor.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.00037 | $0.00682 |
| Opus 5.5 | $0.00015 | $0.00273 |
| Sonnet 5.5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
edge-hint-extractor 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 1mo 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.
This is a copy
100% identical to edge-hint-extractor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edge Hint Extractor
Overview
Convert raw observation signals (market_summary, anomalies, news reactions) into structured edge hints.
This skill is the first stage in the split workflow: observe -> abstract -> design -> pipeline.
When to Use
- You want to turn daily market observations into reusable hint objects.
- You want LLM-generated ideas constrained by current anomalies/news context.
- You need a clean
hints.yamlinput for concept synthesis or auto detection.
Prerequisites
- Python 3.9+
PyYAML- Optional inputs from detector run:
market_summary.jsonanomalies.jsonnews_reactions.csvornews_reactions.json
Output
hints.yamlcontaining:hintslist- generation metadata
- rule/LLM hint counts
Workflow
- Gather observation files (
market_summary,anomalies, optional news reactions). - Run
scripts/build_hints.pyto generate deterministic hints. - Optionally augment hints with LLM ideas via one of two methods:
- a.
--llm-ideas-cmd— pipe data to an external LLM CLI (subprocess). - b.
--llm-ideas-file PATH— load pre-written hints from a YAML file (for Claude Code workflows where Claude generates hints itself).
- a.
- Pass
hints.yamlinto concept synthesis or auto detection.
Note: --llm-ideas-cmd and --llm-ideas-file are mutually exclusive.
Quick Commands
Rule-based only (default output to reports/edge_hint_extractor/hints.yaml):
python3 skills/edge-hint-extractor/scripts/build_hints.py \
--market-summary /tmp/edge-auto/market_summary.json \
--anomalies /tmp/edge-auto/anomalies.json \
--news-reactions /tmp/news_reactions.csv \
--as-of 2026-02-20 \
--output-dir reports/
Rule + LLM augmentation (external CLI):
python3 skills/edge-hint-extractor/scripts/build_hints.py \
--market-summary /tmp/edge-auto/market_summary.json \
--anomalies /tmp/edge-auto/anomalies.json \
--llm-ideas-cmd "python3 /path/to/llm_ideas_cli.py" \
--output-dir reports/
What ships with it
5 files 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.
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.
- 1mo ago First seen · 83 lines · 37 tokens per session scan A 875efa932dbd
edge-hint-extractor is a skill published in the GitHub repository BaggaT236/AI-Trading-Skills (138 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 682 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to edge-hint-extractor, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ib_0dte
Find and place the best 0DTE (zero-days-to-expiration) credit spreads from Interactive Brokers. Default execution route is the EMA9/EMA21 + VIX/VXN regime strategy (emavix0dte.py), which auto-selects bullput or bearcall from a bare EMA cross and skips the trade when the vol index is elevated (VXN ≥ 30 for NDX/QQQ, VIX…
ib-pmcc-advisor
Analyze PMCC (Poor Man's Covered Call / diagonal spread) positions from IB portfolio. For each diagonal spread, reports short leg risk (delta, IV, assignment probability), daily P&L projections, top-3 roll candidates, and a side-by-side comparison table. Requires TWS or IB Gateway running locally.
ib-stop-loss
Downside stop-loss management for PMCC, naked LEAPS, and stock positions in IB. Computes stop prices, detects alerts, and places conditional combo orders. Dry-run by default. Requires TWS or IB Gateway running locally.
ib-trades-history
Fetch trade executions from Interactive Brokers filtered by account, date range, or symbol. Supports live API (7 days history) and FlexReport (full history). Use when user asks about their trades, executions, or transaction history. Requires TWS or IB Gateway running locally.
ib-trailing-stop
Server-side trailing stop management for stocks and naked LEAPS in IB. Places native TRAIL orders that auto-ratchet the stop as price climbs. Dry-run by default. Requires TWS or IB Gateway running locally.
scanner-pmcc
Scan stocks for Poor Man's Covered Call (PMCC) suitability. Analyzes LEAPS and short call options for delta, liquidity, spread, IV, yield, trend direction, and earnings proximity. Use when user asks about PMCC candidates, diagonal spreads, or LEAPS strategies.