agentmods.dev

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.

In plain words
What is it for?
Use it to test the k3s backend, the Docker-based k3d backend, or both in sequence.
Why use it?
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.

Skill for Claude CodeCodex

11 3d ago B scan 44 tokens original Apache-2.0
View the source file ObolNetwork/obol-stack
Install

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.

agentmods
npx agentmods add skills/obolnetwork/obol-stack/test-backend
Any agent
npx skills add ObolNetwork/obol-stack --skill test-backend
Clone the repo
git clone --depth 1 https://github.com/ObolNetwork/obol-stack

Made for: Claude Code, Codex.

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. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.00679
Opus 5 $0.00022 $0.00340
Sonnet 5 $0.00009 $0.00136
Haiku 4.5 $0.00004 $0.00068

Measured 2d ago against content hash c758e3f30bc1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

  1. 2d 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 3d ago), licensed Apache-2.0. It adds 44 tokens to every session and 679 once invoked, about $0.0002 per session on Opus 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.

Backend and APIsE2E testingTestingdappethereumhelmkubernetes
Related

Other skills, from other repositories

test-skill

A minimal test skill for e2e testing of the skill pack resolver.

paperclipinc/openclaw-operator · 19 tokens

regression-tests

Run, scope, or debug telepresence regression tests under regressiontest/ — the integration-level suite. Use when the user wants to run an area, suite, or single test, debug a failure, or says "/regression-tests". Runs go test ./regressiontest scoped with -run, in the background, writing to a log file so heavy output…

telepresenceio/telepresence · 82 tokens

signal-end-to-end

Implements end-to-end signal changes spanning router config, signal extraction, CLI schema, optional bindings, router-owned metadata headers, and E2E test coverage. Use when adding a new signal type, changing signal configuration or extraction logic, updating CLI schema for signal parameters, or modifying router-owned…

vllm-project/semantic-router · 67 tokens

plugin-end-to-end

Implements end-to-end plugin changes spanning router config, post-decision processing, optional CLI/UI exposure, and E2E test coverage. Use when adding a new plugin type, changing plugin config schema or execution semantics, updating plugin chain behavior, or modifying plugin-exposed metadata across surfaces.

vllm-project/semantic-router · 63 tokens

test-pyramid

Analyze the repo's unit and E2E tests and propose rebalancing toward a test pyramid — which E2E tests (or assertions inside them) can be covered by unit tests, which unit-level gaps genuinely need E2E coverage, and where coverage is duplicated. Use when the user asks about test pyramid, test rebalancing, "should this…

kubernetes-sigs/agent-sandbox · 104 tokens

visual-test

Use when visually testing Radar UI changes against a real Kubernetes cluster with Playwright screenshots.

skyhook-io/radar · 20 tokens