omnesis-review SKILL.md skillA
omnesis-review from omnesis-dev/omnesis is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add omnesis-dev/omnesis/omnesis-review@git:20261104.8d35018Pins git:20261104.8d35018 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- omnesis-dev/omnesis
- Path
.agents/skills/omnesis-review/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261104.8d35018, committed Nov 4, 2026
- Size
- 10,152 bytes
- Repository stars
- 53
- License
- AGPL-3.0
Audit Omnesis changes for architecture, correctness, security, privacy, tests, and documentation. Use for a repository review or the required implementation self-review.
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
Audit all code changed in this session — committed, staged, unstaged, and new files — unless the user's accompanying instructions narrow the scope. Only apply checks relevant to those changes. Determine the review base from the requested scope; for a feature branch use `git diff main...HEAD`, then inspect `git diff`, `git diff --cached`, and `git ls-files --others --exclude-standard` to include uncommitted work. Do not infer scope from the number of commits made today. When delegation is available and permitted, use the host agent's sub-agent tools to split relevant checks in parallel. Pass each reviewer the exact file list, review base, and role. Otherwise, work through the full checklist yourself; record any checks you cannot perform. --- ## Checks ### Design and architecture - **Elegance.** Are the abstractions well-considered, or does the code feel like duct tape? Would a staff engineer approve this design? - **Source encapsulation.** No source-specific logic (branching on a source name, unit nouns, icons, URL handling, display strings) outside that source's provider package. The `defineSource()` descriptor is the contract — …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_k67zuvnltfrhjl2k/0e7bb6682bb0f4d3dcb43ef9a2ef6ac7d2548a1a9e3c40f9b4578939d5673147.json
Then /plugin install omnesis-review@markdownregistry-k67zuvnltfrhjl2k in Claude Code. It installs git:20261104.8d35018, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add omnesis-dev/omnesis/omnesis-review@sha256:0e7bb6682bb0f4d3The line at the top of this page pins the label git:20261104.8d35018, 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_k67zuvnltfrhjl2k)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in omnesis-dev/omnesis/omnesis-review since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of omnesis-review from somewhere else? Ask it: where did my omnesis-review come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 4, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/omnesis-review/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (10152 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
omnesis-dev/omnesis · 53 stars · license AGPL-3.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_k67zuvnltfrhjl2k GET https://markdownregistry.com/api/v1/resolve?ref=omnesis-dev/omnesis/omnesis-review GET https://markdownregistry.com/api/v1/blob/0e7bb6682bb0f4d3dcb43ef9a2ef6ac7d2548a1a9e3c40f9b4578939d5673147
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.
More from omnesis-dev/omnesis
Every file in omnesis-dev/omnesis
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.