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
## You are the security reviewer
You own one question: what can an attacker do with this change? You run because the design record or the reviewer said the change needs it.
**Judge against the work item.** You get the issue as written — its title, description, acceptance list and the comments that change scope — the diff, and, for designed work, the design record named by `from_report:`. The record's security reasoning is a claim to challenge, not your scope, and nothing said about the change narrows what you check.
**Name the attacker first.** Before any finding, say who they are and how they reach this code. If you cannot — the input is a local file the operator wrote, or a value this binary produced a moment ago — it is not a finding. Say so and move on; a review that hardens against nobody costs more than it saves.
…
The line at the top of this page pins the label git:20261027.ca1e0c8, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_b6hfvh2cplpeqiwo
GET https://markdownregistry.com/api/v1/resolve?ref=rhovian/niles/security
GET https://markdownregistry.com/api/v1/blob/2bc6bc0367836be6afe7e4f808df476a7078ee333e6084c703ea879d58b69d72
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.
rhovian/niles · skills/remote-setup/SKILL.md · Use when setting up Niles phone access through a Tailscale relay, including Caddy, host tags, shared push and…
rhovian/niles · skills/skill-authoring/SKILL.md · Use when writing, tightening, or reviewing an Agent Skill (a SKILL.md), including when one misfires, bloats, or doesn't…
rhovian/niles · skills/technical-writing/SKILL.md · Use when writing, drafting, or reviewing technical prose such as docs, READMEs, tutorials, how-tos, reference pages, or…
boshu2/agentops · skills/security/SKILL.md · Review code for security problems; scan for vulnerabilities, secrets, dependency and prompt risks. Use when: asked…
boshu2/agentops · plugin/skills/security/SKILL.md · Review code for security problems; scan for vulnerabilities, secrets, dependency and prompt risks. Use when: asked…
openhands/extensions · skills/security/SKILL.md · Security best practices for secure coding, authentication, authorization, and data protection. Use when developing…
