b3os-verification SKILL.md skillA
b3os-verification from b3rys/b3rys-team-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add b3rys/b3rys-team-os/b3os-verification@git:20261030.15e3390Pins git:20261030.15e3390 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- b3rys/b3rys-team-os
- Path
skills/b3os-verification/SKILL.md- Versions recorded
- 11
- Latest version
- git:20261030.15e3390, committed Oct 30, 2026
- First version recorded
- Sep 24, 2026
- Size
- 22,373 bytes
- Repository stars
- 18
- License
- Apache-2.0
b3rys method for proving that a change or a release is correct — and for making that proof hold and get stronger over time. Use when verifying a fix, a feature, or a release candidate; when deciding what to test headless vs in the running app; when a check fails and you must tell a wrong check from a real defect; or when setting up a one-command release check. Covers the 3 principles, the 5 ratchets, a layer + rubric table with numeric pass lines, a triage table for wrong checks…
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
# b3rys Verification — Prove It, and Keep It Proven Where this sits among the team skills: | Skill | Question it answers | |---|---| | `b3os-ai-code-safety` | How do we build it? (structure, refactoring) | | `b3os-sf` | How do we manage and report it? | | `b3os-harness-playbook` | How do we split it across parallel agents? | | **`b3os-verification`** | **How do we prove the result is right — now and on every later change?** | The core idea: a check you set up once must keep protecting you. A new feature or a bug fix ends with **one row in the feature table + a test + a deliberately broken version that the test catches**. The runner does the rest, every time. Passing the runner is evidence for review and approval (TEAM-OS §4), not a substitute for them. **Scope:** §1–5 apply to every change. §6–7 (one app window, the app runner) apply to products with a running app; for server or script work, skip them. --- ## 1. Three principles 1. **Run it; don't read it.** A diagnosis from reading source is a *candidate*. It is not a conclusion until a repro or a measurement confirms it. …
Read the whole file at its exact version.
How to install
mdr add b3rys/b3rys-team-os/b3os-verification@sha256:69bf6fa545db5c7cThe line at the top of this page pins the label git:20261030.15e3390, 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_5mze4u6tbtwu77yi)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 11 versions of this file, between Sep 24, 2026 and Oct 30, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261030.15e3390 latest | 2026-10-30 | 15e3390 | 22,373 B | A | view · diff |
| git:20261027.70fa282 | 2026-10-27 | 70fa282 | 21,956 B | A | view · diff |
| git:20261025.e6b8f4d | 2026-10-25 | e6b8f4d | 20,769 B | A | view · diff |
| git:20261022.5783ea6 | 2026-10-22 | 5783ea6 | 20,384 B | A | view · diff |
| git:20261020.90629a5 | 2026-10-20 | 90629a5 | 18,597 B | A | view · diff |
| git:20261017.f6fa03a | 2026-10-17 | f6fa03a | 15,898 B | A | view · diff |
| git:20261016.a4c2f28 | 2026-10-16 | a4c2f28 | 15,385 B | A | view · diff |
| git:20261003.e9195f7 | 2026-10-03 | e9195f7 | 12,839 B | A | view · diff |
| git:20260927.f9ab9ed | 2026-09-27 | f9ab9ed | 12,849 B | A | view · diff |
| git:20260924.2302b08 | 2026-09-24 | 2302b08 | 11,570 B | A | view · diff |
| git:20260924.19836be | 2026-09-24 | 19836be | 12,511 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 (22373 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
b3rys/b3rys-team-os · 18 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5mze4u6tbtwu77yi GET https://markdownregistry.com/api/v1/resolve?ref=b3rys/b3rys-team-os/b3os-verification GET https://markdownregistry.com/api/v1/blob/69bf6fa545db5c7c258c592ab3777bec1cc612b452d09be14aac04cdb1521d80
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.