correlation-regime skillA
correlation-regime is agent-read markdown (skill) from hkuds/vibe-trading: Correlation-regime detection and crisis attribution — edge-density regime states with hysteresis, causal (no look-ahead) smoothing, regime-aware exposure context, first-mover crisis attribution with honest NAME / MACRO / AMBIGUOUS / ABSTAIN verdicts, and a correlation-rewiring leaderboard that catches slow bleed-outs.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Correlation-Regime Detection and Crisis Attribution ## Overview The `correlation-analysis` skill answers *"how correlated are these assets?"* — a snapshot. This skill answers the temporal questions a snapshot cannot: 1. **When** did the market fuse into one highly-correlated bloc, and when did it release? (Mode 1 — regime detection) 2. **What** does a fused regime mean for position sizing? (Mode 2 — risk context) 3. **Who** moved first when a crisis broke — is there a nameable trigger asset? (Mode 3 — first-mover attribution) 4. **Who** quietly rewired their relationship to the rest of the market, even without a violent move? (Mode 4 — rewiring leaderboard) The methodology comes from an open-source streaming pipeline (see References) whose public repository pins the regime machinery's math and an eight-event historical replay regression (COVID, May-2021, China ban, Nov-2021 top, LUNA, FTX, SVB, yen-carry — 17 crypto symbols, 1-minute bars) that its CI reproduces bit-for-bit. The finer-grained numbers quoted in this skill — 13 fused/defused regime cycles on the continuous 2020–2024 tape at a ~0.008/day calm false-alarm …
Read the whole file at its exact version.
How to install
mdr add hkuds/vibe-trading/correlation-regime@git:20260716.038bf64mdr add hkuds/vibe-trading/correlation-regime@sha256:a77e8d994c3a563cPin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_pizn7syihhx7qlbo)
2 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260716.038bf64 latest | 2026-07-16 | 038bf64 | 21,862 B | A | view · diff |
| git:20260715.c1dab83 | 2026-07-15 | c1dab83 | 21,178 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 (21862 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
hkuds/vibe-trading · 34,089 stars · license MIT · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pizn7syihhx7qlbo GET https://markdownregistry.com/api/v1/resolve?ref=hkuds/vibe-trading/correlation-regime GET https://markdownregistry.com/api/v1/blob/a77e8d994c3a563c92bca6396f2516031fba7f899af5cfb67cc18af3b839261b
Your agent 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.