Borrowing it
Nothing to install: this file belongs to ObolNetwork/obol-stack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ObolNetwork/obol-stack/main/.agents/skills/obol-stack-dev/SKILL.mdgit clone --depth 1 https://github.com/ObolNetwork/obol-stackWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/obolnetwork/obol-stack/obol-stack-dev)<a href="https://agentmods.dev/skills/obolnetwork/obol-stack/obol-stack-dev"><img src="https://agentmods.dev/badge/skills/obolnetwork/obol-stack/obol-stack-dev/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/obolnetwork/obol-stack/obol-stack-dev"><img src="https://agentmods.dev/badge/skills/obolnetwork/obol-stack/obol-stack-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 58 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
What 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.1 | $0.00082 | $0.04328 |
| Opus 5.5 | $0.00033 | $0.01731 |
| Sonnet 5.5 | $0.00016 | $0.00866 |
| Haiku 4.5 | $0.00008 | $0.00433 |
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 13d 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.
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 — 168 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 (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.
- 13d ago Changed 59818d926d94
- 20d ago Changed · +8 lines 2399748ae650
- 1mo ago 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 today), licensed Apache-2.0. It adds 82 tokens to every session and 4,328 once invoked, about $0.0003 per session on Opus 5.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
ethereum-development
Production-grade Ethereum/EVM development workflow for smart contracts, dApps, transactions, clients, gas optimization, testing, security review, deployment, verification, monitoring, and incident response across Foundry, Hardhat, Solidity, TypeScript, viem, ethers, wagmi, and common EVM networks.
Web3 & Blockchain Development
Production-grade Web3 development with Solidity smart contracts, ethers.js/web3.js integration, DApp architecture, security patterns, and AI-enhanced blockchain development (ChatWeb3, Aider + Gemini 2024).
pump-swarm
Coordinated multi-wallet trading on Pump.fun.
trading-solana
Trade tokens on Solana DEXes - Jupiter, Raydium, Orca, Meteora, Pump.fun.
public
For agents: This document explains how to integrate with Clodds APIs.
hyperliquid
Hyperliquid L1 perps DEX (69% market share).