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/distributed-validatorsnpx skills add ObolNetwork/obol-stack --skill distributed-validatorsgit 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.00056 | $0.01403 |
| Opus 5 | $0.00028 | $0.00701 |
| Sonnet 5 | $0.00011 | $0.00281 |
| Haiku 4.5 | $0.00006 | $0.00140 |
Grade C, and why
distributed-validators scanned grade C with 2 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 yesterday.
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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s "https://api.obol.tech/v1/lock/0x..." | python3 -c " Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
metadata: { "openclaw": { "emoji": "🔱", "requires": { "bins": ["curl"] } } } How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Distributed Validators
Monitor distributed validator (DV) clusters using the Obol API. Check cluster health, validator performance, operator status, and exit progress.
A distributed validator splits signing across multiple operators so no single party holds the full key. Obol's middleware (Charon) coordinates this. A cluster has N operators with a threshold (e.g. 3-of-4) needed to sign.
When to Use
- Checking cluster health or validator performance
- Looking up operator reputation or badges
- Checking exit coordination progress
- Exploring network-wide DV statistics
When NOT to Use
- Creating clusters or running DKG (write operations)
- Ethereum RPC queries — use
ethereum-networks - Kubernetes diagnostics — use
obol-stack
API Base
All endpoints are public, no authentication needed:
https://api.obol.tech
Key Identifiers
- lock_hash: Identifies a cluster after key generation (post-DKG).
0x+ 64 hex chars. - config_hash: Identifies a cluster definition before key generation (pre-DKG).
- operator address: Standard Ethereum address,
0x+ 40 hex chars.
Lookup by lock_hash
# Cluster config
curl -s "https://api.obol.tech/v1/lock/0x..."
# Validator performance (0-1 scale, >0.95 is healthy)
curl -s "https://api.obol.tech/v1/effectiveness/0x..."
# Validator beacon chain states
curl -s "https://api.obol.tech/v1/state/0x..."
# Exit status summary
curl -s "https://api.obol.tech/v1/exp/exit/status/summary/0x..."
# Detailed exit status
curl -s "https://api.obol.tech/v1/exp/exit/status/0x..."
Lookup by config_hash
# Pre-DKG cluster definition
curl -s "https://api.obol.tech/v1/definition/0x..."
# Get lock (if DKG completed)
curl -s "https://api.obol.tech/v1/lock/configHash/0x..."
Lookup by operator address
# All clusters for this operator
curl -s "https://api.obol.tech/v1/lock/operator/0x..."
# Reputation level (base < bronze < silver)
curl -s "https://api.obol.tech/v1/address/techne/0x..."
# Protocol badges (Lido, EtherFi, etc.)
curl -s "https://api.obol.tech/v1/address/badges/0x..."
# Terms & conditions signed?
curl -s "https://api.obol.tech/v1/termsAndConditions/0x..."
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.
- yesterday First seen · 160 lines · 56 tokens per session scan C ff4a59fc2246
distributed-validators is a skill published in the GitHub repository ObolNetwork/obol-stack (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,403 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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-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.
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.
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…