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 skills add ObolNetwork/obol-stack --skill obol-stack-front-end-devgit 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-front-end-dev)<a href="https://agentmods.dev/skills/obolnetwork/obol-stack/obol-stack-front-end-dev"><img src="https://agentmods.dev/badge/skills/obolnetwork/obol-stack/obol-stack-front-end-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-front-end-dev"><img src="https://agentmods.dev/badge/skills/obolnetwork/obol-stack/obol-stack-front-end-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00052 | $0.00928 |
| Opus 5.5 | $0.00021 | $0.00371 |
| Sonnet 5.5 | $0.00010 | $0.00186 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
obol-stack-front-end-dev 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 today.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
obol-stack-front-end development (web/frontend)
Run commands from web/frontend in the obol-stack repo.
Quick commands
pnpm install
pnpm run dev:local # localhost:3000 — no cluster
pnpm run dev # obol.stack:3000 + eRPC port-forward
pnpm run test && pnpm run build
pnpm run test:e2e:chromium # mocked APIs — see e2e/README.md
Standalone vs cluster
| Mode | Command | Cluster? |
|---|---|---|
| UI-only | pnpm run dev:local |
No — shows Stack unreachable states |
| Full stack | pnpm run dev after obol stack up |
Yes — /etc/hosts + kubeconfig |
Cluster-backed dev
The dashboard reads the cluster via KUBECONFIG (from obol or NEXT_PUBLIC_KUBECONFIG).
| Surface | API / data source |
|---|---|
| Obol Services | /api/services.json via MARKETPLACE_CATALOG_URL or in-cluster obol-skill-md |
| Sell / ServiceOffers | /api/sell/* → Kubernetes API |
| Agents | /api/agents/* — instances include listing / pendingOffer from agent-listing |
| Marketplace | /api/marketplace/services — ERC-8004 + local catalog |
| x402 probe | POST /api/marketplace/probe — unpaid 402 check (host allowlist) |
From the Mac host when the cluster is up: http://obol.stack:8080 (Traefik). In-pod code uses *.svc.cluster.local — see src/lib/utils/cluster-url.ts.
Deploy dev image to k3d
OBOL_DEVELOPMENT=true obol stack up builds web/frontend as ghcr.io/obolnetwork/obol-stack-front-end:dev-<sha> and imports it (uncommitted changes: OBOL_FORCE_REBUILD_LOCAL_DEV_IMAGES=frontend). Faster loop, from the repo root:
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.
- today First seen · 76 lines · 52 tokens per session scan A f65b1cce187f
obol-stack-front-end-dev is a skill published in the GitHub repository ObolNetwork/obol-stack (11 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 928 once invoked, about $0.0002 per session on Opus 5.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-10-16.
Other skills, from other repositories
securing-helm-chart-deployments
Secure Helm chart deployments by validating chart integrity, scanning templates for misconfigurations, and enforcing security contexts in Kubernetes releases.
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.
helm
Package Kubernetes applications as Helm charts, configure values and dependencies, and inspect release upgrades or rollbacks.
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.
kubernetes-review
Kubernetes & Cloud-Native Review: Reviews Kubernetes manifests, Helm charts, and cloud-native configurations for security, reliability, resource management, and best practices. Covers pods, deployments, services, ingress, RBAC, network policies, HPA, PDB, security contexts, and GitOps patterns. Use when the user…
kubernetes-ontology-access
Use this skill whenever a user wants to onboard, deploy, install, or operate kubernetes-ontology; set up its Helm chart, release CLI, daemon, or topology viewer; run Kubernetes topology queries; diagnose Pod or Workload failures with AI-agent workflows; or connect human visual troubleshooting to the CLI and HTTP API.…