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 commands/zhao73/alphacouncil-agent/alphagit clone --depth 1 https://github.com/Zhao73/alphacouncil-agentWrote 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/zhao73/alphacouncil-agent/alpha)<a href="https://agentmods.dev/commands/zhao73/alphacouncil-agent/alpha"><img src="https://agentmods.dev/badge/commands/zhao73/alphacouncil-agent/alpha.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.03622 |
| Opus 5 | $0.00009 | $0.01811 |
| Sonnet 5 | $0.00003 | $0.00724 |
| Haiku 4.5 | $0.00002 | $0.00362 |
Grade A, and why
alpha 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 4d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/alpha
Request: $ARGUMENTS
Route on the arguments — do not ask what they meant
$ARGUMENTS looks like |
Do this |
|---|---|
| (empty) | Print the mode table below and stop. Do not start a run. |
| a ticker alone, or a question | Full council at the normal pace. Go to "Full council" below. Plugin-managed headless is bound by the selected pace; visible-host execution has no bound at all. |
ticker + fast / slow / deep |
Full council with that tier prefilled. Still show the pace menu and take the answer, exactly as with a named master. |
ticker + quick |
The plugin-managed headless quick_v1 council: 4 fixed analysts, 1-4 selected methods, one parallel bull/bear round and a short PM inside a hard 10-minute ceiling. |
ticker + screen |
screen_ticker only. No language-model judgment, no subagents. |
ticker + options |
get_options_chain only. |
ticker + news |
get_news on the symbol, and on its CIK when it is a US filer. |
market (with or without a theme) |
get_market_narrative. Add the theme as extra_queries. |
When $ARGUMENTS is empty, print exactly this and stop:
/alpha <TICKER> full council — asks how deep to go, then shows every master
/alpha <TICKER> fast same, with the 15-minute tier prefilled
/alpha <TICKER> slow same, with the 60-minute tier prefilled
/alpha <TICKER> quick quick_v1: 4 analysts incl. news + 1-4 masters + 1 parallel debate round (<=10m)
/alpha <TICKER> screen mechanical filings screen only (no model spend)
/alpha <TICKER> options IV term structure, skew, positioning (no model spend)
/alpha <TICKER> news dated filings and headlines (no model spend)
/alpha market <theme> what the market is talking about (no model spend)
you do not have to type a speed: the run asks, and shows the persistence ceiling for each
tier. all three tiers are the same full_v2 contract at three depths; quick is a SMALLER
contract (4 analysts, 1 debate round) and is never full-equivalent
examples
/alpha AAPL /alpha 0700.HK quick /alpha 7203.T news
/alpha NVDA slow /alpha MSFT fast
/alpha NVDA screen /alpha market rates /alpha "is TSM cheap?"
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.
- 4d ago First seen · 217 lines · 17 tokens per session scan A f81a00425137
alpha is a command published in the GitHub repository Zhao73/alphacouncil-agent (3 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 3,622 once invoked, about $0.0001 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 commands, from other repositories
research
Professional equity research analysis with institutional-grade formatting.
jaz-audit-prep
Compile an audit preparation pack in Jaz — generate reports, schedules, and reconciliations for auditor or tax agent.
jaz-gst
Prepare GST/VAT filing in Jaz — review tax ledger, identify discrepancies, generate filing summary.
monitor
AML transaction monitoring and suspicious activity reporting.
paymob-test-cards
Show Paymob sandbox test card and wallet credentials, optionally filtered by payment method.
monitor
Position monitoring — watchlist, thesis check, event radar, thesis tracker, catalyst calendar, morning note.