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:20261107.9fe8f7b, 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: No base64 blob over 200 characters (matched: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA)
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (2078 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 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.
GET https://markdownregistry.com/api/v1/artifacts/art_jsez64ekddtf4usy
GET https://markdownregistry.com/api/v1/resolve?ref=muthuishere/toolnexus/long-desc
GET https://markdownregistry.com/api/v1/blob/ce669569a1349d0713e37ba62431b6b15fab552ec35f6093d902d0add061c201
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.
muthuishere/toolnexus · .claude/skills/marketing/SKILL.md · Draft and track the launch posts (LinkedIn, X, Hacker News, Reddit) for a toolnexus release in…
muthuishere/toolnexus · .claude/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
muthuishere/toolnexus · .claude/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
muthuishere/toolnexus · .claude/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
muthuishere/toolnexus · .claude/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
muthuishere/toolnexus · .claude/skills/openspec-sync-specs/SKILL.md · Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta…
muthuishere/toolnexus · .claude/skills/release/SKILL.md · Cut and verify a toolnexus release across all eight registries, with the guardrails that a green CI run does not give…
muthuishere/toolnexus · clojure/examples/clj-ex1/skills/clojure-events/SKILL.md · Use when asked about Clojure community events, meetups or conferences. How to fetch and report them.
muthuishere/toolnexus · clojure/examples/cljgo-ex1/skills/clojure-events/SKILL.md · Use when asked about Clojure community events, meetups or conferences. How to fetch and report them.
ivy00johns/skill-madness · tests/installer/fixtures/skills/meta/long-desc/SKILL.md · Apply long-desc when testing that description length above 500 characters produces only a WARN and never an ERROR. Use…
pachara-n/skills-lint · test/fixtures/broken/long-desc/SKILL.md · This description is intentionally far too long to pass the agent skills specification limit and it keeps repeating…
