harness-watch SKILL.md skillA
harness-watch from uze-sh/uze is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add uze-sh/uze/harness-watch@git:20261014.fd0b4a7Pins git:20261014.fd0b4a7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- uze-sh/uze
- Path
.agents/skills/harness-watch/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261014.fd0b4a7, committed Oct 14, 2026
- First version recorded
- Oct 7, 2026
- Size
- 8,932 bytes
- Repository stars
- 3
- License
- Apache-2.0
Surveying what the supported harnesses (Claude Code, Codex, OpenCode, Antigravity CLI) shipped since UZE last looked, and judging each change against UZE's own integrations — use whenever someone asks what is new in a harness, to read the vendors' changelogs or release notes, whether a vendor release breaks or improves an integration, whether a declared limitation or an Unsupported delivery can become native, or before planning integration work. Covers the baseline each survey starts from, the…
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
# Watching the harnesses
UZE's integrations encode beliefs about four products that move every week:
which mechanism is native, which control is missing, which file a harness
reads. A belief written down months ago is the most likely thing to be wrong
in `crates/uze-integrations/`. This survey re-asks those beliefs against what
the vendors shipped, and reports which ones changed.
It is research. It produces a report and stops: no code, no ADR, no
`expected.json` edit until the operator picks a finding to act on.
## Step 1 — the baseline: since when
Each survey starts from the version UZE last proved, not from a date in
memory. `conformance/evidence/<harness>.json` records it:
```bash
for h in claude codex opencode antigravity; do
python3 -c "import json;d=json.load(open('conformance/evidence/$h.json'));print('$h',d['harness_version'],d['recorded_at'])"
done
```
Everything released after `harness_version` is in scope. If the evidence is
older than about two months, say so in the report: the gap itself is a
finding.
The tool snapshots are the second baseline, and the sharper one:
`conformance/evidence/tools/<harness>.json` holds, for the version it names,
…Read the whole file at its exact version.
How to install
mdr add uze-sh/uze/harness-watch@sha256:d922e961af6b27dfThe line at the top of this page pins the label git:20261014.fd0b4a7, 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_kltyxfwwiidkx44b)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 7, 2026 and Oct 14, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.fd0b4a7 latest | 2026-10-14 | fd0b4a7 | 8,932 B | A | view · diff |
| git:20261007.3aa314d | 2026-10-07 | 3aa314d | 8,848 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 (8932 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
uze-sh/uze · 3 stars · license Apache-2.0 · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kltyxfwwiidkx44b GET https://markdownregistry.com/api/v1/resolve?ref=uze-sh/uze/harness-watch GET https://markdownregistry.com/api/v1/blob/d922e961af6b27df6e82cd461a50bb410c7c5be5481623fd6a2903f1fb341c3a
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.