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/obolnetwork/obol-stack/autoresearchnpx skills add ObolNetwork/obol-stack --skill autoresearchgit clone --depth 1 https://github.com/ObolNetwork/obol-stackWhat 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.00024 | $0.01226 |
| Opus 5 | $0.00012 | $0.00613 |
| Sonnet 5 | $0.00005 | $0.00245 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
autoresearch 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autoresearch
Autonomous LLM optimization: the agent iterates on train.py, runs 5-minute GPU experiments, measures validation bits-per-byte (val_bpb), and publishes the best checkpoint as a sellable Ollama model.
When to Use
- Optimizing a base model for a specific domain or task
- Running automated training experiments to improve val_bpb
- Publishing an optimized model checkpoint to Ollama
- Selling an optimized model via x402 payment-gated inference
When NOT to Use
- Selling an existing model without optimization — use
sell - Buying remote inference — use
buy-x402 - Cluster diagnostics — use
obol-stack
Quick Start
1. Prepare Data
Place your training and validation data in the autoresearch working directory:
autoresearch/
train.bin # training data (tokenized)
val.bin # validation data (tokenized)
train.py # training script (agent modifies this)
results.tsv # experiment log (appended by each run)
2. Run Experiments
The agent modifies train.py and runs experiments in a loop. Each experiment:
- Has a 5-minute time budget on GPU
- Produces a checkpoint and a val_bpb measurement
- Is tracked as a git commit with status (keep/discard) in
results.tsv
The results.tsv file is tab-separated with columns:
commit_hash val_bpb status description
a1b2c3d 1.042 keep baseline transformer
e4f5g6h 1.038 keep added RMSNorm
i7j8k9l 1.051 discard unstable lr schedule
3. Publish the Best Model
Once experiments are complete, use publish.py to find the best checkpoint, register it with Ollama, and optionally sell it:
# Publish to Ollama only
python3 scripts/publish.py /path/to/autoresearch
# Publish and sell via x402
python3 scripts/publish.py /path/to/autoresearch \
--sell \
--wallet 0xYourWalletAddress \
--price 0.002 \
--chain base-sepolia
Commands
| Command | Description |
|---|---|
publish.py <dir> |
Find best experiment, create Ollama model, generate provenance |
publish.py <dir> --sell --wallet <addr> --price <p> --chain <c> |
Publish and sell via obol sell inference |
What ships with it
1 file 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 · 135 lines · 24 tokens per session scan A 01572cc5991c
autoresearch is a skill published in the GitHub repository ObolNetwork/obol-stack (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 24 tokens to every session and 1,226 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.
Other skills, from other repositories
kurtosis-ethereum
Run Ethereum multi-client devnets using Kurtosis and the ethpandaops/ethereum-package. Use for spinning up local devnets, syncing public testnets, validating cross-client interop, testing fork transitions, shadowforks, running assertoor checks, debugging CL/EL client interactions, or verifying new feature…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
nvca-self-managed-install
Install or validate the NVCA Operator chart against a self-managed NVCF control plane from the native monorepo. Use when the control plane comes from deploy/stacks/self-managed and NVCA must be installed with stack-derived image repository settings.
nvca-values-customization
Customize NVCA Operator Helm chart values in the native monorepo. Use when modifying vendored defaults, changing stack-derived install values, adding deployment-time overrides, or updating scripts under deploy/helm/nvca-operator.
test-skill
A minimal test skill for e2e testing of the skill pack resolver.
release-chart
Cut and publish a new release of the Zabbix Helm chart in this repository, following the versioning rules and maintainer release process documented in CONTRIBUTING.md and CLAUDE.md (bump Chart.yaml/artifacthub-pkg.yml/values.yaml, regenerate docs, tag the release so CI publishes it). Trigger on requests like "release…