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/monetize-guidenpx skills add ObolNetwork/obol-stack --skill monetize-guidegit 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.00104 | $0.02662 |
| Opus 5 | $0.00052 | $0.01331 |
| Sonnet 5 | $0.00021 | $0.00532 |
| Haiku 4.5 | $0.00010 | $0.00266 |
Grade C, and why
monetize-guide 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 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.
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 http://localhost:11434/api/tags | python3 -c " Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:11434/api/tags | python3 -c " How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monetize Guide
Step-by-step guide to expose local GPU resources or HTTP services as x402 payment-gated endpoints with on-chain discovery via ERC-8004.
When to Use
- User says "monetize my machine", "sell my GPU", or "expose my service for payments"
- Setting up a new paid endpoint from scratch
- Need to figure out what to sell and at what price
When NOT to Use
- Managing existing offers (list/status/delete) — use
selldirectly - Buying inference from others — use
buy-x402 - Cluster diagnostics — use
obol-stack
Workflow
Follow these phases in order. Stop and ask the user for confirmation before executing phase 4.
Phase 1: Pre-flight Checks
Verify the environment is ready before proceeding.
# 1. Check cluster is running
obol kubectl get nodes
# 2. Check the agent is initialized (has RBAC for monetization)
obol kubectl get clusterrolebinding openclaw-monetize-read-binding -o jsonpath='{.subjects}'
# 3. Get the wallet address (auto-generated by agent)
python3 ${OBOL_SKILLS_DIR:-/data/.openclaw/skills}/ethereum-local-wallet/scripts/signer.py accounts
If cluster is not running: Tell the user to run obol stack up first. Do NOT run it yourself — it takes several minutes and changes system state.
If agent has no RBAC subjects: Tell the user to run obol agent init.
If no wallet address: The wallet is created during obol stack up. If missing, the stack may not have completed setup.
Phase 2: Detect What Can Be Sold
For GPU / Inference
# Check what Ollama models are available locally
curl -s http://localhost:11434/api/tags | python3 -c "
import json, sys
data = json.load(sys.stdin)
for m in data.get('models', []):
size_gb = m.get('size', 0) / 1e9
print(f\" {m['name']:30s} {size_gb:.1f} GB\")
"
Report the available models to the user. If no models are found, suggest they pull one:
ollama pull qwen3.5:4b # Smallest current Qwen, ~3.4 GB (low-RAM laptops)
ollama pull qwen3.5:9b # Validated baseline, ~6.6 GB
ollama pull qwen3.6:27b # High quality, ~17 GB (needs ≥32GB RAM)
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 · 284 lines · 104 tokens per session scan C 2e1942a70134
monetize-guide is a skill published in the GitHub repository ObolNetwork/obol-stack (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 104 tokens to every session and 2,662 once invoked, about $0.0005 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…