verify-hyperfide SKILL.md skillB
verify-hyperfide from sidiora-labs/codify is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sidiora-labs/codify/verify-hyperfide@git:20261023.611d35bPins git:20261023.611d35b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sidiora-labs/codify
- Path
platform/.hyperfide/skills/verify-hyperfide/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261023.611d35b, committed Oct 23, 2026
- Size
- 13,153 bytes
- Repository stars
- 423
- License
- MIT
Verify HYPERFIDE user journeys in an isolated source dev app using dev-browser@next and the matching source CLI. Use after HYPERFIDE feature changes or when asked to verify or smoke-test HYPERFIDE. The feature map covers core UI and agent interfaces, every repository plugin, desktop, mobile, and hosted services; select the affected recipes and platform prerequisites.
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 HYPERFIDE Run from the repository root. Start with [the feature map](features/README.md) and select the affected journeys. Read `docs/debugging-and-qa.md` for the source development workflow. The launch below targets the source web app and local host daemon. Desktop, native mobile, and hosted services have additional setup in their feature files. A pass on one platform does not verify another. ## Coverage and selection The feature map aims to inventory every feature discoverable in this checkout, including disabled plugins, compatibility paths, and developer surfaces. Group files contain individual capability recipes. Read only the relevant files for a focused verification request; for an exhaustive audit, track every recipe. Mark each selected recipe `passed`, `failed`, `not run`, or `blocked` with its specific prerequisite and evidence. Group-level source coverage never upgrades an unexecuted recipe to a pass. Run the read-only inventory check before selecting coverage: ```bash .hyperfide/skills/verify-hyperfide/scripts/inventory.py ``` Python 3 and Git are required. The check compares source declarations and …
Read the whole file at its exact version.
How to install
mdr add sidiora-labs/codify/verify-hyperfide@sha256:c3a125b7c532805bThe line at the top of this page pins the label git:20261023.611d35b, 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_gbn6z7mqfwjc5g6d)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 23, 2026.
Audit of the latest version
- fail: No link to a raw IP address (matched: http://127.0.0.1)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13153 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 script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
sidiora-labs/codify · 423 stars · license MIT · pushed 2026-10-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gbn6z7mqfwjc5g6d GET https://markdownregistry.com/api/v1/resolve?ref=sidiora-labs/codify/verify-hyperfide GET https://markdownregistry.com/api/v1/blob/c3a125b7c532805bfbefa62929c9b60c5f8fc96090d15e0b8c652f0f28ab4249
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.