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/obol-stack-devnpx skills add ObolNetwork/obol-stack --skill obol-stack-devgit 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.00082 | $0.04024 |
| Opus 5 | $0.00041 | $0.02012 |
| Sonnet 5 | $0.00016 | $0.00805 |
| Haiku 4.5 | $0.00008 | $0.00402 |
Grade A, and why
obol-stack-dev scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| flow-03 step 3 / flow-04: tool-call not returned, agent HTTP 000 | The QA vLLM endpoint was relaunched without its tool-call/reasoning parser flags (`--enable-auto-tool-choice --tool-call-parser ... --reasoning-parser 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.
Obol Stack Dev
Operational router. Load only the reference for the task. Do not delegate understanding — read the relevant reference yourself; subagents lose context the next reference would have given them.
CLI-First Rule
Prefer the supported obol CLI surface for every stack operation: obol stack,
obol model, obol agent, obol sell, obol buy, obol network, obol tunnel, and obol kubectl for inspection. Do not create ad-hoc shell scripts
or verifier scripts. Do not bypass CLI behavior with direct script execution,
raw kubectl mutation, or ConfigMap surgery when an obol command exists.
Existing repository flow scripts are release-gate artifacts, not the default QA
interface. Use them only when the user explicitly asks for release-smoke/full
flow validation or when no CLI equivalent exists; otherwise decompose checks
into CLI commands plus obol kubectl evidence.
Reference Router
| Need | Read |
|---|---|
| Local build, env vars, force-rebuild, CLI surface | references/dev.md |
| PR trains, ordered merge/collapse, release candidate gate | references/release-train.md |
| Release-smoke broken — what to check first | references/release-smoke-debugging.md |
| Live OBOL smoke, flow choice, Bob derivation, success criteria | references/paid-flows.md |
| LiteLLM model setup, paid/* route, port-forward | references/llm-routing.md |
| Remote QA worktrees, tmux, scoped cleanup | references/remote-qa.md |
| Integration tests (BDD + tunnel + sell/buy roundtrip) | references/integration-testing.md |
| Catch-all gotchas (ca-certs, RBAC race, port drift) | references/troubleshooting.md |
First Actions on Any Task
- Read existing files before changing anything.
- Use
obolCLI andobol kubectlfirst; do not invent or run ad-hoc scripts. - New worktree per remote QA run.
- Never write hostnames, personal paths, passwords, private keys, or raw tokens into skill files, PR text, or commit messages.
- Validate with the narrowest command set that covers the change.
- On a dev branch (anything not at the latest release tag), set
OBOL_DEVELOPMENT=trueforobolup.shandobol stack up. Without it,obolup.shdownloads the released binary and your branch changes never run. Replace thego runwrapper with a real binary before long QA (go build -o .workspace/bin/obol ./cmd/obol) so every CLI call uses the same branch build.
What ships with it
8 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.
- yesterday First seen · 160 lines · 82 tokens per session scan A 12e0a4d13acd
obol-stack-dev is a skill published in the GitHub repository ObolNetwork/obol-stack (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 82 tokens to every session and 4,024 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (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…