peer-cited-platform-limit-may-be-a-conflation SKILL.md skillA
peer-cited-platform-limit-may-be-a-conflation 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/peer-cited-platform-limit-may-be-a-conflation@v1.1.0Pins v1.1.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/peer-cited-platform-limit-may-be-a-conflation/SKILL.md- Versions recorded
- 2
- Latest version
- v1.1.0, committed Sep 21, 2026
- First version recorded
- Sep 17, 2026
- Size
- 10,045 bytes
- Repository stars
- 3
- License
- MIT
A coordinator or peer session hands you a constraint stated as a platform fact ("the provider's ceiling forbids N workers, so that run is not a machine you could buy"), and it is their own conflation of two quantities that happen to share a number in today's configuration. Use when: (1) a peer message tells you an option is impossible, unsupported or not purchasable, and names no source; (2) you are about to drop a measurement arm, narrow a brief or tell the user an option does not exist, on…
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 Peer's Cited Platform Limit May Be Their Own Conflation ## Problem A coordinating session sends a brief that is mostly right — the ordering, the budget, the reporting format, the thing to measure — and one sentence in it states a platform limit that does not exist: > "12 workers is above the provider's 8-CPU ceiling for a job task, so that arm > is a cost-per-worker measurement, not a machine the user could actually buy. > Do not let it read as an option." The instruction that follows is reasonable, the tone is certain, and the rest of the message is verifiable and correct. Accepting it costs an arm of the measurement and tells the user an option does not exist. **It was a conflation of two different quantities: worker PROCESSES and CPUs.** The provider's published ceiling is on vCPU and memory per task. Nothing in it constrains how many worker processes the task starts. Twelve workers on an eight-CPU task is legal and deployable; it means twelve processes sharing eight CPUs, each slower, each still paying its own memory. ## Why it survives being written down **The two quantities share a number in the current configuration.** Production …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/peer-cited-platform-limit-may-be-a-conflation@sha256:145d70ad9e4b4ca1The line at the top of this page pins the label v1.1.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_6hp3ara3w72e6dnw)
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 21, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-09-21 | 772e9c1 | 10,045 B | A | view · diff |
| v1.0.0 | 2026-09-17 | 95260a8 | 7,246 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 (10045 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_6hp3ara3w72e6dnw GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/peer-cited-platform-limit-may-be-a-conflation GET https://markdownregistry.com/api/v1/blob/145d70ad9e4b4ca139df3a81dbed2ece15d84773e50a85cb615f4d23acb339fc
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.