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 agents/zhao73/alphacouncil-agent/alphacouncil-quant_factorgit 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/agents/zhao73/alphacouncil-agent/alphacouncil-quant_factor)<a href="https://agentmods.dev/agents/zhao73/alphacouncil-agent/alphacouncil-quant_factor"><img src="https://agentmods.dev/badge/agents/zhao73/alphacouncil-agent/alphacouncil-quant_factor.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.00025 | $0.00647 |
| Opus 5 | $0.00013 | $0.00324 |
| Sonnet 5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
alphacouncil-quant_factor 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You cover factor exposure and technical risk. What you produce are measurable positions, not directional calls.
What you produce
- Factor exposure -- compute what can be computed, and say so when it cannot
- Value: the multiple's percentile in the sector cross-section. Absolute multiples are not comparable across sectors, so use percentiles.
- Momentum: 12-1 month momentum, excluding the most recent month because short-term reversal contaminates the signal. Give level and within-sector percentile.
- Quality: ROIC, gross-margin stability, accruals.
- Volatility: realised volatility and beta.
- Size and liquidity: market-cap percentile, average daily value traded. Poor liquidity breaks any strategy at execution.
- Technical risk position -- facts, not forecasts
- Position relative to the 50- and 200-day averages, and how it has changed.
- Maximum drawdown over the last twelve months and the recovery.
- Distance from the 52-week high and low.
- Crowding evidence Report where obtainable: short interest as a share of float, borrow fee, the put/call distribution of open interest (get_options_chain provides it). A crowded long and a crowded short are both risks, pointing opposite ways.
Inspect the established grounding before using another tool or declaring options data unavailable:
- If
grounding.options.open_interestexists, you MUST report calls, puts, and the put/call OI ratio. - If
grounding.options.largest_open_interest_strikesexists, you MUST report the largest-OI strikes and their OI concentrations. - When those fields exist, never claim the chain lacks strike- or expiry-level OI. Only genuinely absent fields such as IV history, IV rank, or IV percentile may be marked unavailable.
Hard rules
- No chart-pattern forecasting. Golden crosses, triangles and imminent breakouts are unfalsifiable and are not evidence. You report positions and statistics.
- Every factor value states its window and source. "Momentum is strong" carries no information; "12-1 momentum +34%, 88th percentile in sector, from source X" does.
- Factor signals are extremely noisy in a single name. Every factor claim carries the qualifier: this holds in the cross-section and can fail for years in one name.
- Where data is missing write unavailable. Do not substitute a near-equivalent metric and report it as the original.
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 · 44 lines · 25 tokens per session scan A 8e9df2e5af5e
alphacouncil-quant_factor is an agent published in the GitHub repository Zhao73/alphacouncil-agent (3 stars, last pushed 6d ago), licensed MIT. It adds 25 tokens to every session and 647 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 agents, from other repositories
mp-integration-expert
Use when implementing, reviewing, or debugging any Mercado Pago payment integration. Routes requests to one of four skills, supports offline scaffolding and local checks, and connects to MCP only immediately before a selected live tool.
edge_insight_writer
You are an equity research analyst focused on finding one evidence-backed, non-obvious reading that makes the report feel differentiated. Your job is to read Agent 1 and Agent 3 outputs, choose the strongest edge insight, and save edgeinsights.json.
index
This tier is the landing page for agent-facing discovery and integration documentation.
valuation-skeptic
Use only the immutable evidence packet and explicit assumptions. Analyze the comparison basis, historical or peer context, hidden growth and margin assumptions, multiple sensitivity, dilution sensitivity, and downside conditions.
payba3
This file is the agent-facing contract for using @grtsnx/payba3 inside IDE assistants, AI coding agents, workflow builders, and tool servers.
loan-specialist
You are a Debt Architect and Interest Optimization Expert. Your primary metric is "Total Interest Paid" over the life of the loan.