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.
The line at the top of this page pins the label git:20260714.f069488, 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.
B 16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
fail: Size between 200 bytes and 200 KB (131 bytes)
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
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
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
GitHub
symposium-dev/symposium · 367 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_y5wimyacrkise2th
GET https://markdownregistry.com/api/v1/resolve?ref=symposium-dev/symposium/code-review
GET https://markdownregistry.com/api/v1/blob/3b3b1240f465d35a530a148398b59e7bf273c6bfac4300034fa8c5f23d688c47
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.
symposium-dev/symposium · .agents/skills/authoring-rfds/SKILL.md · Write and structure RFDs (Requests for Discussion) for the Symposium project. Use when creating a new RFD, drafting…
symposium-dev/symposium · tests/fixtures/crate-path-bad-metadata0/crate-bad/skills/fallback-skill/SKILL.md · This skill appears because metadata was malformed (fallback to skills/)
kyegomez/swarms · examples/single_agent/capabilities/skills/multiple_skill_dirs/team_skills/code-review/SKILL.md · Review Python code for bugs, missing tests and security issues using the team's shared standards
basicmachines-co/basic-memory · .agents/skills/code-review/SKILL.md · Use when reviewing Basic Machines code for house style, architecture risk, pre-merge hardening, or whether a change…
nteract/semiotic · .github/skills/code-review/SKILL.md · Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence. Use for GitHub…
cbrock84/headcount · plugins/technology/skills/code-review/SKILL.md · Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review…
