binary-sync-verify SKILL.md skillA
binary-sync-verify from aqaddora/gaza-geo-sync is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add aqaddora/gaza-geo-sync/binary-sync-verify@git:20261006.6d6c75bPins git:20261006.6d6c75b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- aqaddora/gaza-geo-sync
- Path
.claude/skills/binary-sync-verify/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261006.6d6c75b, committed Oct 6, 2026
- Size
- 2,386 bytes
- Repository stars
- 11
- License
- MIT
Measure and test a gaza-geo-sync integration - payload bytes before/after, round-trip correctness of JSON vs binary, strict decoding, upload request rate - and report honestly. Use after integrating or migrating to the binary position format, or when asked whether the binary sync is actually smaller/faster.
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
# Verify a binary position sync
## 1. Correctness (must pass before any numbers)
- **Round-trip:** for the same server state, `Accept: application/json` and
`Accept: application/octet-stream` must yield the same records after `fetchPositions`
(lat/lon equal after `codec.round`, speed within `speedStep/2`, time within 1 s).
Pattern: `tests/sync.test.ts` → "JSON and binary decode to identical payloads".
- **Strict decoder:** truncated, trailing-byte, wrong-version, wrong-profile and random inputs
throw `CodecError` and nothing else (`tests/fuzz.test.ts` pattern, 20,000 inputs).
- **Fallback:** a client sending no Accept header gets JSON; a server answering JSON is
handled by the client; an upload refused with 400 is retried as JSON.
- **Offline:** with the network off, the screens read the cached JSON records unchanged.
## 2. Bytes
```bash
# JSON as most proxies send it (gzip) vs binary. Run against your dev server.
curl -s -o /dev/null -w 'json %{size_download} B\n' -H 'Accept-Encoding: gzip' -H 'Accept: application/json' "$URL"
curl -s -o /dev/null -w 'bin %{size_download} B\n' -H 'Accept-Encoding: gzip' -H 'Accept: application/octet-stream' "$URL"
…Read the whole file at its exact version.
How to install
mdr add aqaddora/gaza-geo-sync/binary-sync-verify@sha256:97a8f38ccae3224fThe line at the top of this page pins the label git:20261006.6d6c75b, 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_gixpi2rf6vjmakrp)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 6, 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 (2386 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
aqaddora/gaza-geo-sync · 11 stars · license MIT · pushed 2026-10-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gixpi2rf6vjmakrp GET https://markdownregistry.com/api/v1/resolve?ref=aqaddora/gaza-geo-sync/binary-sync-verify GET https://markdownregistry.com/api/v1/blob/97a8f38ccae3224f5dd9cb94cadec7996252c1566f24e2f2f8ba37f7bcf6ffa1
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.