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/discoverynpx skills add ObolNetwork/obol-stack --skill discoverygit 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.00055 | $0.01447 |
| Opus 5 | $0.00028 | $0.00724 |
| Sonnet 5 | $0.00011 | $0.00289 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
discovery 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery
Discover AI agents registered on the ERC-8004 Identity Registry. Query on-chain data to find agents, inspect their registration metadata, and fetch their service endpoints.
When to Use
- Finding other AI agents registered on-chain
- Looking up an agent's registration URI, owner, or wallet address
- Fetching and displaying an agent's registration JSON (services, capabilities)
- Counting total registered agents on a chain
- Searching recent registrations to discover new agents
When NOT to Use
- Registering your own agent on-chain -- use
sell(ServiceOffer with ERC-8004 registration stage) - Sending transactions or signing -- use
ethereum-local-wallet - General Ethereum queries (balances, blocks) -- use
ethereum-networks - Cluster diagnostics -- use
obol-stack
Quick Start
# Search for recently registered agents on Base mainnet (default)
python3 scripts/discovery.py search
# Search on mainnet with a limit
python3 scripts/discovery.py search --chain mainnet --limit 5
# Get details for a specific agent by ID
python3 scripts/discovery.py agent 42
# Fetch and display the agent's registration JSON from their URI
python3 scripts/discovery.py uri 42
# Count total registered agents
python3 scripts/discovery.py count
# Look up agent on mainnet
python3 scripts/discovery.py agent 1 --chain mainnet
Commands
| Command | Description |
|---|---|
search [--chain <network>] [--limit N] |
List recently registered agents from on-chain events |
agent <id> [--chain <network>] |
Get agent details: tokenURI, owner, wallet |
uri <id> [--chain <network>] |
Fetch the agent's registration JSON from their URI |
count [--chain <network>] |
Total number of registered agents |
Supported Chains
The ERC-8004 Identity Registry is deployed at the same address on 20+ chains via CREATE2:
| Chain | Network Name | Registry Address |
|---|---|---|
| Base (default) | base |
0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 |
| Base Sepolia | base-sepolia |
0x8004A818BFB912233c491871b3d84c89A494BD9e |
| Sepolia | sepolia |
0x8004A818BFB912233c491871b3d84c89A494BD9e |
| Mainnet | mainnet |
0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 |
| Base | base |
0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 |
| Arbitrum | arbitrum |
0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 |
| Optimism | optimism |
0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 |
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 · 143 lines · 55 tokens per session scan A a58a58971a97
discovery is a skill published in the GitHub repository ObolNetwork/obol-stack (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,447 once invoked, about $0.0003 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-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…