orchestrator-rule-too-strict-stalls-agent-silently SKILL.md skillA
orchestrator-rule-too-strict-stalls-agent-silently 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/orchestrator-rule-too-strict-stalls-agent-silently@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/orchestrator-rule-too-strict-stalls-agent-silently/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Sep 2, 2026
- Size
- 11,007 bytes
- Repository stars
- 3
- License
- MIT
A safety rule you wrote into an agent's brief can be so strict that its precondition never holds — and the agent then does exactly the right thing, which is nothing, for as long as you leave it running. Nothing errors, nothing goes red, and the agent's own status reads as work in progress, so the stall is invisible from every surface you would normally check. Use when: (1) an agent has been running a long time with no product and no failure; (2) you gave an agent a guard phrased over the WHOLE…
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
# Your own rule is the blocker, and it fails silently ## Problem You write a guard into an agent's brief to stop it doing something dangerous. The guard is correct in spirit and its precondition is scoped too wide, so in a busy environment it never holds. The agent obeys. It checks the precondition, finds it unmet, waits, checks again. It is behaving exactly as instructed and it produces nothing. **Every surface that would normally tell you says the wrong thing:** | Surface | What it shows | What it means | |---|---|---| | the agent's status | running | it is running | | CI | green / nothing new | nothing was pushed | | the PR list | open, no new activity | nobody merged anything | | the agent's own notes | "waiting for the safe window" | the window will never open | There is no error to find, and a correctly-waiting agent is indistinguishable from a busy one. This is what makes an over-strict rule more expensive than a wrong one: a wrong rule usually breaks something and tells you. **The observed cost:** a landing agent was told that `gh pr update-branch` was safe only when **nothing was running repo-wide**. In a repo with several lanes pushing all …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/orchestrator-rule-too-strict-stalls-agent-silently@sha256:2ab8b8f2594e27c5The 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_wuzqit3jzocau3eq)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 2, 2026.
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 (11007 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_wuzqit3jzocau3eq GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/orchestrator-rule-too-strict-stalls-agent-silently GET https://markdownregistry.com/api/v1/blob/2ab8b8f2594e27c5105dba0a02249e038a7327f18a9f903b9f57303e13b3eff0
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.