Borrowing it
Nothing to install: this file belongs to sgl-project/rbg. 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/sgl-project/rbg/main/.claude/skills/stress-test/SKILL.mdgit clone --depth 1 https://github.com/sgl-project/rbgWrote 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/sgl-project/rbg/stress-test)<a href="https://agentmods.dev/skills/sgl-project/rbg/stress-test"><img src="https://agentmods.dev/badge/skills/sgl-project/rbg/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/sgl-project/rbg/stress-test"><img src="https://agentmods.dev/badge/skills/sgl-project/rbg/stress-test.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 23 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.00039 | $0.04315 |
| Opus 5.5 | $0.00016 | $0.01726 |
| Sonnet 5.5 | $0.00008 | $0.00863 |
| Haiku 4.5 | $0.00004 | $0.00432 |
Grade A, and why
stress-test 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 2mo 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.
- `helm`, `kubectl`, `go`, `curl` available in PATH How it starts
The opening of the file, as written. The whole thing — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RBG Controller Stress Test
This skill orchestrates a full stress test of the RBG controller. It supports two modes:
- Manual mode: User defines all parameters, skill runs tests and outputs analysis report
- Auto-tuning mode: User defines the workload scenario, skill runs multiple rounds and recommends optimal controller resource/QPS/burst configuration
Architecture
The stress test uses in-cluster kwok to simulate workload pods:
- kwok controller + stage-fast deployed via Helm in the existing cluster
- Fake nodes created with
type=kwoklabel andkwok.x-k8s.io/nodetaint - RBG controller runs as a real Pod (via Helm) on real nodes with configurable resources
- Stress test workload pods schedule to fake nodes and are simulated as Ready by kwok
- This allows testing controller performance without needing real GPU/compute resources
Prerequisites
- A Kubernetes cluster accessible via current kubeconfig
helm,kubectl,go,curlavailable in PATH- RBG CRDs and controller already deployed (or will be deployed by this skill)
Workflow
Phase 1: Ask User for Scenario
Use AskUserQuestion to gather parameters:
Question 1 - Test Mode:
- Manual mode (user sets all params, get report)
- Auto-tuning mode (auto-iterate to find optimal config)
Question 2 - Controller Resources (affects scheduling and memory):
- 4c/8g (small)
- 8c/16g (medium, recommended)
- 16c/32g (large)
- 32c/64g (extra-large)
Question 3 - Controller Parameters:
- max-concurrent-reconciles: 5, 10, 20, 50
- kube-api-qps: 20 (default), 50, 100, 200
- kube-api-burst: 30 (default), 100, 200, 400
Question 4 - RBG Workload Template:
- Roles per RBG: 2, 3, 5
- LeaderWorkerPattern roles: 0, 1, 2
- LWS size (pods per instance): 2, 4, 8
- Total RBG instances: 10, 50, 100, 500, 1000
Question 5 - QPS for Operations:
- Create QPS: 1, 5, 10, 20
- Update QPS: 1, 5, 10, 20
- Delete QPS: 1, 5, 10, 20
Question 6 - In-place Update:
- Yes (update image to trigger InPlaceIfPossible)
- No (update annotations to trigger RollingUpdate with RecreatePod)
What ships with it
1 file 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.
- 2mo ago First seen · 426 lines · 39 tokens per session scan A 1620cdfb4406
stress-test is a skill published in the GitHub repository sgl-project/rbg (312 stars, last pushed 2d ago), licensed Apache-2.0. It adds 39 tokens to every session and 4,315 once invoked, about $0.0002 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
local-test
Build, run, and test IronClaw locally using Docker containers and Chrome MCP browser automation.
kubernetes-expert
Expert-level Kubernetes cluster management, deployment strategies, networking, and production operations. Use when the user mentions containers, orchestration, devops, or cloud native, or when the task involves Kubernetes Architecture, Pods, Deployments, or Services.
kubernetes
Kubernetes operations expert for kubectl, pods, deployments, and debugging.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
darwinian-evolver
Evolve prompts/regex/SQL/code with Imbue's evolution loop.