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/minihellboy/factorminer/factor-miningnpx skills add minihellboy/factorminer --skill factor-mininggit clone --depth 1 https://github.com/minihellboy/factorminerWhat 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.00091 | $0.00742 |
| Opus 5 | $0.00046 | $0.00371 |
| Sonnet 5 | $0.00018 | $0.00148 |
| Haiku 4.5 | $0.00009 | $0.00074 |
Grade A, and why
factor-mining 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Factor Mining
This skill runs FactorMiner's self-evolving discovery loop: it retrieves memory priors, proposes candidate factor formulas with an LLM, evaluates them, and admits the survivors to a factor library.
See references/loop-architecture.md for the stage-by-stage loop design and references/dsl-operators.md for the factor-formula operator vocabulary.
Choosing the loop
| Use | When |
|---|---|
mine (Ralph loop) |
Default. Paper-faithful Algorithm 1 — retrieve, generate, evaluate, admit, evolve memory. |
helix (Helix loop) |
When you want Phase 2 features: do-calculus causal validation, regime-conditional evaluation, multi-specialist debate generation, or SymPy canonicalization. Drop-in superset of Ralph. |
Workflow
1. Confirm prerequisites
The dataset must already pass factor-data validation. Confirm the iteration budget — mining cost scales with iterations × batch-size.
2. Run the Ralph loop
factorminer -o output/run1 mine \
--data path/to/market_data.csv \
--iterations 40 --batch-size 16 --target 30
--iterations— maximum mining iterations (the loop also stops early once--targetfactors are admitted).--batch-size— candidate factors proposed per iteration.--target— desired library size.--resume path/to/factor_library.json— continue a previous run.--mock— synthetic data + mock LLM, no API calls. Use only for smoke tests.
3. Or run the Helix loop
factorminer -o output/run1 helix \
--data path/to/market_data.csv \
--iterations 40 --batch-size 16 --target 30 \
--causal --regime --debate --canonicalize
Each --feature / --no-feature flag overrides the config; omit a flag to keep the config default. Phase 2 features cost extra compute and LLM calls — enable the ones the research question needs.
4. Inspect the result
factorminer session inspect output/run1 --json
Report library size, iteration count, and yield rate. The factor library is written to output/run1/factor_library.json; the run log to session_log.json.
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 · 67 lines · 91 tokens per session scan A 8c48229bc3b3
factor-mining is a skill published in the GitHub repository minihellboy/factorminer (105 stars, last pushed 16d ago), licensed MIT. It adds 91 tokens to every session and 742 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…