job-reports-success-while-its-worker-was-oom-killed SKILL.md skillA
job-reports-success-while-its-worker-was-oom-killed 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/job-reports-success-while-its-worker-was-oom-killed@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/job-reports-success-while-its-worker-was-oom-killed/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Sep 22, 2026
- First version recorded
- Sep 17, 2026
- Size
- 8,387 bytes
- Repository stars
- 3
- License
- MIT
A batch or cloud job lists as SUCCEEDED while the work inside it produced nothing, because the kernel's out-of-memory killer took a forked WORKER and the parent caught the failure, wrote its record and exited 0. Use when: (1) a run's own output says a worker "died"/"was terminated abruptly" but the execution listing says succeeded, (2) you are about to report "the job failed" or "the run died" to a coordinator who will quote you upstream, (3) a peer checks the listing, sees success and tells…
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
# A Job Reports SUCCESS While Its Worker Was OOM-Killed ## Problem A long research run fans routing work out to forked worker processes. One worker is killed by the kernel's out-of-memory killer. The parent process catches the resulting "a process in the process pool was terminated abruptly", records the failure in its own JSON, writes its log and returns 0 — which is correct behaviour for a harness that reports rather than crashes. The result is three artefacts that disagree in a way nobody notices: | artefact | what it says | |---|---| | the execution listing | `succeededCount 1`, condition `Completed True` | | the run's own record | the work raised "a worker died while routing item 10 of 100", zero results written | | the platform's logs | nothing about memory at all | So "the run died" is wrong, "the run succeeded" is wrong, and the useful sentence is longer than either. ## Why the platform says nothing about memory A managed runtime emits its memory-limit message when it kills the CONTAINER. A child process killed inside a container that stays alive is invisible to it: the task did not exceed anything the platform enforces, and from outside, nothing …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/job-reports-success-while-its-worker-was-oom-killed@sha256:0d0355c26c142328The 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_5vwurlksis3tl525)
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 | 8,387 B | A | view · diff |
| v1.0.0 | 2026-09-17 | 95260a8 | 7,811 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 (8387 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_5vwurlksis3tl525 GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/job-reports-success-while-its-worker-was-oom-killed GET https://markdownregistry.com/api/v1/blob/0d0355c26c142328ffcd12890c8752cadf03f90bb92792c7e6db31bd9105e661
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.