evaluate

A command that measures how well a factor library performs on data held back from development. IC measures signal correlation, ICIR relates that signal to its variability, and decay shows how performance changes over time.

In plain words
What is it for?
Use it to recompute out-of-sample metrics on a test split, compare training and test performance, and identify factors whose results decay.
Why use it?
It prevents a factor from being accepted based only on results from the data used to create it.

Command

Install

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.

agentmods
npx agentmods add commands/minihellboy/factorminer/evaluate
Clone the repo
git clone --depth 1 https://github.com/minihellboy/factorminer
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 105 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00105
Opus 5 $0.00008 $0.00053
Sonnet 5 $0.00003 $0.00021
Haiku 4.5 $0.00002 $0.00011

Measured 2d ago against content hash 34c3ad9355fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

evaluate 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.

integrations/factor-researcher/plugin/commands/evaluate.md · 10 lines

What it actually says

Load the factor-evaluation skill and recompute the library's metrics on the held-out test split. Lead with out-of-sample numbers, and run --period both to surface train→test decay. Report honestly — an in-sample-only factor is a rejected factor.

Changes

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.

  1. 2d ago First seen · 10 lines · 16 tokens per session scan A 34c3ad9355fc

Subscribe to this mod's changes

evaluate is a command published in the GitHub repository minihellboy/factorminer (105 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 105 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-30.