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 sector-analystgit 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/sector-analyst)<a href="https://agentmods.dev/skills/baggat236/ai-trading-skills/sector-analyst"><img src="https://agentmods.dev/badge/skills/baggat236/ai-trading-skills/sector-analyst/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/sector-analyst"><img src="https://agentmods.dev/badge/skills/baggat236/ai-trading-skills/sector-analyst.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.00077 | $0.01594 |
| Opus 5 | $0.00039 | $0.00797 |
| Sonnet 5 | $0.00015 | $0.00319 |
| Haiku 4.5 | $0.00008 | $0.00159 |
Grade A, and why
sector-analyst 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 12d 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 sector-analyst — 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sector Analyst
Overview
This skill enables comprehensive analysis of sector and industry performance charts to identify market cycle positioning and predict likely rotation scenarios. The analysis combines observed performance data with established sector rotation principles to provide objective market assessment and probabilistic scenario forecasting.
When to Use This Skill
Use this skill when:
- User provides sector performance charts (typically 1-week and 1-month timeframes)
- User provides industry performance charts showing relative performance data
- User requests analysis of current market cycle positioning
- User asks for sector rotation assessment or predictions
- User needs probability-weighted scenarios for market positioning
Example user requests:
- "Analyze these sector performance charts and tell me where we are in the market cycle"
- "Based on these performance charts, what sectors should outperform next?"
- "What's the probability of a defensive rotation based on this data?"
- "Review these sector and industry charts and provide scenario analysis"
Analysis Workflow
Follow this structured workflow when analyzing sector/industry performance charts:
Step 1: Data Collection and Observation
First, carefully examine all provided chart images to extract:
- Sector-level performance: Identify which sectors (Technology, Financials, Consumer Discretionary, etc.) are outperforming/underperforming
- Industry-level performance: Note specific industries showing strength or weakness
- Timeframe comparison: Compare 1-week vs 1-month performance to identify trend consistency or divergence
- Magnitude of moves: Assess the size of relative performance differences
- Breadth of movement: Determine if performance is concentrated or broad-based
Think in English while analyzing the charts. Document specific numerical performance figures for key sectors and industries.
Step 2: Market Cycle Assessment
Load the sector rotation knowledge base to inform analysis:
- Read
references/sector_rotation.mdto access market cycle and sector rotation frameworks - Compare observed performance patterns against expected patterns for each cycle phase:
- Early Cycle Recovery
- Mid Cycle Expansion
- Late Cycle
- Recession
What ships with it
4 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.
- 12d ago First seen · 207 lines · 77 tokens per session scan A 36901b95fd77
sector-analyst is a skill published in the GitHub repository BaggaT236/AI-Trading-Skills (121 stars, last pushed 8d ago), licensed MIT. It adds 77 tokens to every session and 1,594 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sector-analyst, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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.
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.
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-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.
stock_analyzer
A stock and market analysis skill that returns structured information about trends, prices, news, risks, catalysts, and possible trading plans.
ib-find-short-roll
Find roll options for existing short positions OR find best covered call/put to open against long stock. Use when user asks about rolling shorts, finding roll candidates, writing covered calls, or managing option positions. Requires TWS or IB Gateway running locally.