create-slash-commands-dtd SKILL.md skillA
create-slash-commands-dtd from nova-violet-role/rot-dtd-commander is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nova-violet-role/rot-dtd-commander/create-slash-commands-dtd@git:20260916.b7506d7Pins git:20260916.b7506d7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nova-violet-role/rot-dtd-commander
- Path
src/skills/create-slash-commands-dtd/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260916.b7506d7, committed Sep 16, 2026
- First version recorded
- Sep 2, 2026
- Size
- 19,659 bytes
- Repository stars
- 3
- License
- AGPL-3.0
Expert guidance for creating Claude Code slash commands. Use when working with slash commands, creating custom commands, understanding command structure, or learning YAML configuration. Carries its own DOCTYPE: a declared output grammar, a trust boundary and laws the checker enforces.
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
<!-- SPDX-License-Identifier: (AGPL-3.0-or-later OR EUPL-1.2) AND MIT --> <!-- Copyright 2026 Saimonokuma. --> <!-- Portions Copyright 2025 Lex Christopherson, MIT (taches-cc-resources); see NOTICE.md. --> <!-- SPDX-FileCopyrightText: 2025 Lex Christopherson (taches-cc-resources, MIT) --> <!DOCTYPE command_creation [ <!ENTITY % cc-core SYSTEM "../../../dtd/cc-core.dtd"> %cc-core; <!ENTITY % cc-ask SYSTEM "../../../dtd/cc-ask.dtd"> %cc-ask; <!ELEMENT command_creation (intake, frontmatter, doctype, body, verification)> <!ELEMENT intake (#PCDATA)> <!ELEMENT frontmatter (#PCDATA)> <!ELEMENT doctype (#PCDATA)> <!ELEMENT body (#PCDATA)> <!ELEMENT verification (#PCDATA)> <!ENTITY LAW.CMD.1 "A generated command carries frontmatter with a description, then a DOCTYPE whose root is declared and named in the body, then a trust_boundary, then objective, process, output_format with a grammar_map, and success_criteria invoking its LAW entities."> <!ENTITY LAW.CMD.2 "The command is reported done only after rdc check passes on it."> ]> <trust_boundary> Declared in the DOCTYPE above and binding for this run: …
Read the whole file at its exact version.
How to install
mdr add nova-violet-role/rot-dtd-commander/create-slash-commands-dtd@sha256:9ab084a6352cc4a1The line at the top of this page pins the label git:20260916.b7506d7, 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_e2szjpiwmxeltno5)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 2, 2026 and Sep 16, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.b7506d7 latest | 2026-09-16 | b7506d7 | 19,659 B | A | view · diff |
| git:20260911.9a4d65f | 2026-09-11 | 9a4d65f | 19,133 B | A | view · diff |
| git:20260907.f163678 | 2026-09-07 | f163678 | 19,008 B | A | view · diff |
| git:20260902.622f086 | 2026-09-02 | 622f086 | 18,914 B | A | view · diff |
| git:20260902.0a9600a | 2026-09-02 | 0a9600a | 18,912 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 (19659 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
nova-violet-role/rot-dtd-commander · 3 stars · license AGPL-3.0 · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e2szjpiwmxeltno5 GET https://markdownregistry.com/api/v1/resolve?ref=nova-violet-role/rot-dtd-commander/create-slash-commands-dtd GET https://markdownregistry.com/api/v1/blob/9ab084a6352cc4a10a50ee2e31c89766d09d32d5663d6f220f14bcc4a6fec316
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 nova-violet-role/rot-dtd-commander
Every file in nova-violet-role/rot-dtd-commander