What is test-backend?

An integration test for the Obol Stack backend using k3s or k3d, two ways to run Kubernetes, a system for managing containers. It tests the backend from setup through shutdown and cleanup.

Use it to test the k3s backend, the Docker-based k3d backend, or both in sequence.

It checks the complete backend lifecycle instead of testing isolated commands. This can reveal problems that occur when the cluster is created, used, stopped, or removed.

How ObolNetwork/obol-stack configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/ObolNetwork/obol-stack/main/.agents/skills/test-backend/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ObolNetwork/obol-stack

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/obolnetwork/obol-stack/test-backend/github.svg)](https://agentmods.dev/skills/obolnetwork/obol-stack/test-backend)

Your own site

<a href="https://agentmods.dev/skills/obolnetwork/obol-stack/test-backend"><img src="https://agentmods.dev/badge/skills/obolnetwork/obol-stack/test-backend/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/obolnetwork/obol-stack/test-backend"><img src="https://agentmods.dev/badge/skills/obolnetwork/obol-stack/test-backend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 679 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00044	$0.00679
Opus 5.5	$0.00018	$0.00272
Sonnet 5.5	$0.00009	$0.00136
Haiku 4.5	$0.00004	$0.00068

Measured 1mo ago against content hash c758e3f30bc1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

test-backend scanned grade B 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 1mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/test-k3d.sh, scripts/test-k3s.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- **all**: Run k3s first, then k3d (k3s requires sudo so test it first while credentials are fresh)

.agents/skills/test-backend/SKILL.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Backend Skill

Runs a full lifecycle integration test for the obol stack backend (k3d or k3s).

Arguments

The skill accepts an optional argument specifying which backend to test:

k3s - Test the k3s (bare-metal) backend only
k3d - Test the k3d (Docker-based) backend only
all - Test both backends sequentially (default)
No argument defaults to all

Examples:

/test-backend k3s
/test-backend k3d
/test-backend all
/test-backend (same as all)

Workflow

1. Pre-flight

Build the obol binary: go build -o .workspace/bin/obol ./cmd/obol from the project root
Verify the binary was created successfully
Set OBOL_DEVELOPMENT=true and add .workspace/bin to PATH

2. Run Test Script

Based on the argument, run the appropriate test script(s) located alongside this skill:

k3s: Run .agents/skills/test-backend/scripts/test-k3s.sh
k3d: Run .agents/skills/test-backend/scripts/test-k3d.sh
all: Run k3s first, then k3d (k3s requires sudo so test it first while credentials are fresh)

Execute the script via Bash tool from the project root directory. The scripts require:

k3s: Linux, sudo access, k3s binary in .workspace/bin/
k3d: Docker running, k3d binary in .workspace/bin/

3. Report Results

After each script completes, report:

Total pass/fail counts (shown in the RESULTS line)
Any specific test failures with their names
Overall verdict: all green or needs attention

If a test script fails (non-zero exit), read the output to identify which test(s) failed and summarize.

Important Notes

The k3s backend requires NOPASSWD sudo or cached credentials (sudo -v) — the Bash tool has no TTY for interactive password prompts
The k3d backend requires Docker to be running
Each test script performs its own cleanup (purge) before and after
Tests are sequential and ordered: init -> up -> verify -> down -> restart -> purge
Typical runtime: ~2-4 minutes per backend
If the environment has issues (Docker not starting, k3s not installing), report the problem clearly rather than retrying endlessly

Read the full file on GitHub · 71 lines

Files

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.

Changes

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.

1mo ago First seen · 71 lines · 44 tokens per session scan B c758e3f30bc1

Subscribe to this mod's changes

test-backend is a skill published in the GitHub repository ObolNetwork/obol-stack (11 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 679 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Containers DevOps and cloud E2E testing Testing dapp ethereum helm kubernetes

verify

Build the computer-use-demo image and drive the Streamlit UI headlessly to verify changes end-to-end.

anthropics/claude-quickstarts · 23 tokens

mirrord-chaos

Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…

metalbear-co/mirrord · 119 tokens

obol-stack: Skill for Claude Code