stress-test-run SKILL.md skillA
stress-test-run from baristaze/swe_guidelines is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add baristaze/swe_guidelines/stress-test-run@git:20261014.62aa70ePins git:20261014.62aa70e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- baristaze/swe_guidelines
- Path
scaffold/acme_root/.agents/skills/stress-test-run/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261014.62aa70e, committed Oct 14, 2026
- First version recorded
- Sep 29, 2026
- Size
- 9,648 bytes
- Repository stars
- 94
- License
- MIT
Run one stress test scenario of the system against one environment with the system's own generator, read the signals back through their own APIs, and report pass or fail against a target stated before the run: the scenario's p95 and error ratio, or the one the run states instead. A real run is the system developer's choice; the CI sanity run is thirty seconds at the light profile and is never a stress test. Needs the read-only investigate profile to read the signals back.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# stress-test-run The generator at the scenario's profile, for the scenario's duration, then the signals, then a verdict. The target is the scenario's unless the run states its own; either way it is stated before the run, and the verdict names it and where it came from. Read `../_shared/ops-preamble.md`, a path from this skill's folder, before the first step: the profiles, the account check, and the env file are there. ## Input `<name> --env local|staging|production [--p95-ms <ms>] [--error-ratio <ratio>] [--report <path>]` `<name>` names `ops/stress/<name>.yaml` and is required; `--env` is required; ask for either when missing. `--p95-ms` and `--error-ratio` state the pass mark for this one run, one number or both; without them the scenario's own is judged. They are given before the run, never after it: a target picked once the numbers are in is not a target. A generous one with a short `--duration` is a wiring check; a strict one on the same scenario is the run worth reading. `--report` writes the run's table as JSON beside printing it; the verdict is printed, not written to the file. `local` runs against the compose stack and needs no cloud; it proves the scenario …
Read the whole file at its exact version.
How to install
mdr add baristaze/swe_guidelines/stress-test-run@sha256:ae609f3f1aa2147cThe line at the top of this page pins the label git:20261014.62aa70e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mbkfpqsaojqdq4k5)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 29, 2026 and Oct 14, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.62aa70e latest | 2026-10-14 | 62aa70e | 9,648 B | A | view · diff |
| git:20260930.97478f9 | 2026-09-30 | 97478f9 | 9,661 B | A | view · diff |
| git:20260930.6756f8f | 2026-09-30 | 6756f8f | 9,370 B | A | view · diff |
| git:20260929.0713568 | 2026-09-29 | 0713568 | 9,361 B | A | view · diff |
| git:20260929.3422014 | 2026-09-29 | 3422014 | 9,177 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9648 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
baristaze/swe_guidelines · 94 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mbkfpqsaojqdq4k5 GET https://markdownregistry.com/api/v1/resolve?ref=baristaze/swe_guidelines/stress-test-run GET https://markdownregistry.com/api/v1/blob/ae609f3f1aa2147c916991c3327cf09b708e7191e1bd35c064910b8fcba1e99b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.