parallel-gate-legs-killed-for-memory-count-cannot-see-ram SKILL.md skillA
parallel-gate-legs-killed-for-memory-count-cannot-see-ram from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/parallel-gate-legs-killed-for-memory-count-cannot-see-ram@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/parallel-gate-legs-killed-for-memory-count-cannot-see-ram/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Sep 22, 2026
- First version recorded
- Sep 17, 2026
- Size
- 15,983 bytes
- Repository stars
- 3
- License
- MIT
Two sessions run local test legs on the same machine and one session's leg is killed for memory mid-run, while the concurrency guard everybody uses — a count of running test processes — reads well inside its limit the whole time. Use when: (1) a background test run ends with a harness notice like "stopped because the system is running low on memory" and its log simply stops, with no traceback, no summary line and no exit code, (2) you are about to re-report that leg as RED, (3) your…
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
# Parallel Gate Legs Killed for Memory — the Count Cannot See RAM ## Problem Two sessions share one developer machine. Each runs the repo's local test legs before pushing, and each obeys a concurrency rule of the form *"at most two heavy legs machine-wide"*, implemented as a count of running test processes. Your background leg dies. What you get is not a failure: the log **stops**, with no traceback, no `N passed` summary and no exit status, and the harness says the task was stopped because the system was low on memory. The count, sampled throughout, read **1**. Three wrong conclusions are one step away, and all three are natural: 1. **"My leg went red."** It did not run to a verdict at all. 2. **"My loop is broken."** The obvious fix — restart it — walks straight back into the same collision, because nothing about the machine changed. 3. **"The concurrency rule did not fire, so concurrency was not the problem."** The rule cannot see the resource that ran out. ## Context / Trigger Conditions - A `run_in_background` test leg ends with a low-memory notice, or its output file ends mid-run with no summary …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/parallel-gate-legs-killed-for-memory-count-cannot-see-ram@sha256:a7e96b6ad5baa427The line at the top of this page pins the label v1.0.0, 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_ujq3ugkcukwmwyup)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 17, 2026 and Sep 22, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-22 | 27778c6 | 15,983 B | A | view · diff |
| v1.0.0 | 2026-09-17 | e5ca372 | 11,969 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 (15983 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
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ujq3ugkcukwmwyup GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/parallel-gate-legs-killed-for-memory-count-cannot-see-ram GET https://markdownregistry.com/api/v1/blob/a7e96b6ad5baa4276f156a998736a7c7f2e870da3f91a6d24ac89e56df3c1bd3
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.