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.
git 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/commands/baggat236/ai-trading-skills/scenario-analyzer)<a href="https://agentmods.dev/commands/baggat236/ai-trading-skills/scenario-analyzer"><img src="https://agentmods.dev/badge/commands/baggat236/ai-trading-skills/scenario-analyzer/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/commands/baggat236/ai-trading-skills/scenario-analyzer"><img src="https://agentmods.dev/badge/commands/baggat236/ai-trading-skills/scenario-analyzer.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.00036 | $0.00863 |
| Opus 5 | $0.00018 | $0.00432 |
| Sonnet 5 | $0.00007 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
scenario-analyzer 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 scenario-analyzer — 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scenario Analyzer
Analyze 18-month scenarios from a news headline and assess the impact on sectors and stocks.
Arguments
$ARGUMENTS
Argument interpretation:
- If a headline is included: analyze that headline
- If the argument is empty: ask the user to enter a headline
Usage examples:
/scenario-analyzer Fed raises rates by 50bp→ analyze the Fed rate-hike scenario/scenario-analyzer China announces new tariffs on US semiconductors→ analyze the tariff scenario/scenario-analyzer OPEC+ agrees to cut oil production→ analyze the oil production-cut scenario/scenario-analyzer→ ask for a headline, then analyze
Analysis Contents
| Item | Description |
|---|---|
| Related news | Collect related articles from the past 2 weeks via WebSearch |
| Scenarios | 3 scenarios (Base/Bull/Bear) with probabilities |
| Impact analysis | 1st-/2nd-/3rd-order sector impact |
| Stock selection | 3-5 positive and 3-5 negative stocks (US market) |
| Review | Second opinion (points out blind spots / biases) |
Execution Procedure
-
Headline parsing:
- Extract the headline from the argument
- If the argument is empty, ask the user for input
- Classify the event type (Monetary Policy / Geopolitics / Regulation / Technology / Commodities / Corporate)
-
Load references:
Read skills/scenario-analyzer/references/headline_event_patterns.md Read skills/scenario-analyzer/references/sector_sensitivity_matrix.md Read skills/scenario-analyzer/references/scenario_playbooks.md -
Main analysis (scenario-analyst agent):
Agent tool: - subagent_type: "scenario-analyst" - prompt: headline + event type + reference informationOutput:
- List of related news articles
- 3 scenarios (Base/Bull/Bear)
- Sector impact analysis (1st/2nd/3rd-order)
- List of recommended stocks
-
Second opinion (strategy-reviewer agent):
Agent tool: - subagent_type: "strategy-reviewer" - prompt: full text of the Step 3 analysis result
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 · 105 lines · 36 tokens per session scan A d65c44971d77
scenario-analyzer is a command published in the GitHub repository BaggaT236/AI-Trading-Skills (121 stars, last pushed 9d ago), licensed MIT. It adds 36 tokens to every session and 863 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to scenario-analyzer, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
finalize
Final investment recommendations with full context - reads all research, advises user, executes approved trades.
alpha
Scan for alpha opportunities and spawn parallel research agents.
positions
Review all open positions with parallel subagents. Decides HOLD or SELL for each position.
desk
Show active agents, connected exchanges, portfolio status, and KPI dashboard.
fire
Deactivate an underperforming trading agent.
backtest
Test a trading strategy on historical data.