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/refraction-ray/xalpha/question2reportnpx skills add refraction-ray/xalpha --skill question2reportgit clone --depth 1 https://github.com/refraction-ray/xalphaWhat 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.00075 | $0.03002 |
| Opus 5 | $0.00037 | $0.01501 |
| Sonnet 5 | $0.00015 | $0.00600 |
| Haiku 4.5 | $0.00007 | $0.00300 |
Grade A, and why
question2report 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 2d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Question → Report Skill
Transform a user's free-form financial question into a production-quality, self-contained HTML report with embedded charts and tables.
Pipeline
User Question
│
▼
┌──────────────────┐
│ 1. ANALYZE │ Parse intent, identify assets, metrics, time range
└────────┬─────────┘
│
▼
┌──────────────────┐
│ 2. CONFIRM │ Present analysis plan to user; agree on scope
└────────┬─────────┘
│
▼
┌──────────────────┐
│ 3. DISCOVER API │ Explore the xalpha codebase to find suitable APIs
└────────┬─────────┘
│
▼
┌──────────────────┐
│ 4. FETCH & CLEAN │ Write & run a Python script; handle errors & NaN
└────────┬─────────┘
│
▼
┌──────────────────┐
│ 5. ANALYZE DATA │ Compute metrics appropriate to the question
└────────┬─────────┘
│
▼
┌──────────────────┐
│ 6. GENERATE HTML │ Build a beautiful, self-contained HTML report
└──────────────────┘
Step 1 — Analyze the Question
Parse the user's natural-language question and extract:
- Subject: What assets, funds, indices, or strategies are being discussed?
- Comparison / benchmark: Is there a reference to compare against?
- Time range: Explicit dates, or implied ("last 3 years", "since inception"). Default to the most recent 3 full calendar years if unspecified.
- Desired output: What kind of insights does the user want? (rankings, trend comparison, risk analysis, prediction accuracy, etc.)
If fund codes or asset identifiers are not given, research them via web search or by exploring the xalpha codebase for relevant list/search APIs.
Step 2 — Confirm Scope
Before any data work, present a concise plan to the user:
📋 Analysis Plan
─────────────────────────────────
Subject : <what is being analyzed>
Assets : <list of codes / tickers>
Period : <start> → <end>
Analysis : <what metrics / comparisons will be computed>
Charts : <what visualizations will be included>
─────────────────────────────────
Shall I proceed, or would you like to adjust?
What ships with it
2 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.
- 2d ago First seen · 248 lines · 75 tokens per session scan A 8644d4e6ed65
question2report is a skill published in the GitHub repository refraction-ray/xalpha (2,688 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 3,002 once invoked, about $0.0004 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-30.
Other skills, from other repositories
dcf-model
DCF valuation: free cash flow projections, WACC, terminal value, sensitivity analysis.
comps-analysis
Comparable company analysis: operating metrics, valuation multiples, peer benchmarking.
initiating-coverage
Full equity research initiation: company research, financial model, valuation, charts, 30-50 page report.
ui-design
Design-quality reference for financial-research visual output: typography, color, composition, and avoiding generic AI aesthetics.
onboarding
First-time user onboarding to set up investment profile, watchlists, portfolio, and preferences.
user-profile
Manage user profile including watchlists, portfolio, and preferences.