Borrowing it
Nothing to install: this file belongs to AlexanderMattTurner/agent-glovebox. 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/AlexanderMattTurner/agent-glovebox/main/.claude/skills/stress-test/SKILL.mdgit clone --depth 1 https://github.com/AlexanderMattTurner/agent-gloveboxWrote 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/alexandermattturner/agent-glovebox/stress-test)<a href="https://agentmods.dev/skills/alexandermattturner/agent-glovebox/stress-test"><img src="https://agentmods.dev/badge/skills/alexandermattturner/agent-glovebox/stress-test/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/alexandermattturner/agent-glovebox/stress-test"><img src="https://agentmods.dev/badge/skills/alexandermattturner/agent-glovebox/stress-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.01586 |
| Opus 5 | $0.00037 | $0.00793 |
| Sonnet 5 | $0.00015 | $0.00317 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
stress-test 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 6d 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.
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stress Test Skill
Generate smoke and stress tests for infrastructure components (sandbox runtimes, network isolation, container orchestration, entrypoint hardening, cross-platform setup). Prioritize end-to-end realism over unit-test purity — the goal is catching setup issues that surface on real platforms (Linux, macOS Colima/OrbStack, WSL2). Also fires on "make sure this works on macOS/Linux/WSL2".
General test-quality rules — test behavior not source text, non-vacuity, parametrize repeated patterns, no duplicate coverage, fixtures for repeated I/O — come from the writing-tests skill; follow it. This skill adds the infra-specific shape on top.
Principles
- Two tiers, always both. Static config validation (pytest, no Docker, runs everywhere) + live runtime checks (bash, needs Docker, proves isolation actually works).
- Assert the operation, not a keyword.
assert "chown -R root:root" in contentcatches the real behavior;assert "chown" in contentalso matches a comment. Prefer the invariant/relationship (e.g. "proxy env vars reference the firewall's IP", read from both sides) over a hardcoded value that breaks on a legitimate config change. - Guard empty-vs-empty. When comparing values that could be empty (namespace readlinks), assert non-empty first — an empty-vs-empty comparison silently passes.
- Bash checks are self-contained. Each check passes/fails/warns independently via a
FAILUREScounter, notset -e(which kills the whole script on one non-critical failure). PrintPASS:/FAIL:prefixes for grep-ability. - Test what breaks per platform. macOS: volume mounts (virtiofs/9p) and runtime install (Colima SSH). Linux: KVM availability and cgroup drivers. WSL2: nested virtualization.
Workflow
1. Identify the component and inventory existing tests
Determine what's under test (the sbx microVM launch and its kata runtime, the guest egress filter, entrypoint hardening, the host-side monitor and audit sink, setup scripts). Search tests/ and bin/check-*.bash for existing coverage and list it, so you extend rather than duplicate.
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.
- 6d ago Changed 4eff5968d503
- 11d ago First seen · 77 lines · 74 tokens per session scan A a85af545ecbe
stress-test is a skill published in the GitHub repository AlexanderMattTurner/agent-glovebox (62 stars, last pushed yesterday), licensed Apache-2.0. It adds 74 tokens to every session and 1,586 once invoked, about $0.0004 per session on Opus 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-08-30.
Other skills, from other repositories
verify
Build the computer-use-demo image and drive the Streamlit UI headlessly to verify changes end-to-end.
zero-script-qa
Zero Script QA — test without scripts using structured JSON logging and Docker monitoring. Triggers: zero-script-qa, log testing, docker logs, QA.
local-test
Build, run, and test IronClaw locally using Docker containers and Chrome MCP browser automation.
wiremock-standalone-docker
Provides patterns and configurations for running WireMock as a standalone Docker container. Generates mock HTTP endpoints, creates stub mappings for testing, validates integration scenarios, and simulates error conditions. Use when you need to mock APIs, create a mock server, stub external services, simulate…
branchbox-devcontainer-guardrails
Use when modifying BranchBox devcontainer/bootstrap workflows, compose templates, feature env-stash behavior, or manual E2E harness/release docs. Apply issue.
configure-webhook-bdd-test
Configure the Docker Compose webhook receivers required by the VIOS webhook notification BDD tests, including the custom body template cases. Use when preparing deployment/stream-processing/docker-compose/configs/notificationconfig.json for testwebhooknotifications.py or testwebhookcustombody.py, or when those tests…