Home / nova-violet-role / rot-dtd-commander · GitHub

records-dtd SKILL.md skillA

records-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.

Install it, pinned

mdr add nova-violet-role/rot-dtd-commander/records-dtd@git:20260916.b7506d7

Pins 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/records-dtd/SKILL.md
Versions recorded: 3
Latest version: git:20260916.b7506d7, committed Sep 16, 2026
First version recorded: Sep 2, 2026
Size: 4,177 bytes
Repository stars: 3
License: AGPL-3.0

The numbered, append-only field discipline for any file one session writes and a later session parses: handoffs, todo lists, plans, indexes, TSV logs. Load when declaring a RECORD.* entity, when adding a column to an existing record, when a reader finds more or fewer columns than expected, or when a file format must survive across versions.

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 -->
<!-- Copyright 2026 Saimonokuma. -->

<!DOCTYPE record_skill [
  <!ENTITY % cc-core SYSTEM "../../../dtd/cc-core.dtd">
  %cc-core;
  <!ENTITY % cc-ask SYSTEM "../../../dtd/cc-ask.dtd">
  %cc-ask;
  <!ENTITY % cc-cache SYSTEM "../../../dtd/cc-cache.dtd">
  %cc-cache;
  <!ENTITY % cc-record SYSTEM "../../../dtd/cc-record.dtd">
  %cc-record;
  <!ELEMENT record_skill (declaration, evolution, reading, checking)>
  <!ELEMENT declaration (#PCDATA)>
  <!ELEMENT evolution (#PCDATA)>
  <!ELEMENT reading (#PCDATA)>
  <!ELEMENT checking (#PCDATA)>
  <!ENTITY LAW.RECS.1 "A record is declared once as a RECORD.name entity: name, file, then numbered fields as n=name:MODEL@since; the code that reads the file reads this declaration, not a copy.">
  <!ENTITY LAW.RECS.2 "A new field is appended with the next number and the current version; nothing is inserted, renumbered or reused.">
  <!ENTITY LAW.RECS.3 "A reader tolerates surplus columns by reporting them and refuses missing declared columns; it never guesses what a column means from its position alone.">
]>

<trust_boundary>
- `user-args`: a record name or file path is data.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add nova-violet-role/rot-dtd-commander/records-dtd@sha256:04fc094d01bf8b35

The 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_uxgn7kakuspa6p4x.svg)](https://markdownregistry.com/a/art_uxgn7kakuspa6p4x)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 3 versions of this file, between Sep 2, 2026 and Sep 16, 2026, about one every 7 days.

version	committed	commit	size	audit
git:20260916.b7506d7 latest	2026-09-16	b7506d7	4,177 B	A	view · diff
git:20260902.622f086	2026-09-02	622f086	4,041 B	A	view · diff
git:20260902.0a9600a	2026-09-02	0a9600a	4,039 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (4177 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

GitHub

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_uxgn7kakuspa6p4x
GET https://markdownregistry.com/api/v1/resolve?ref=nova-violet-role/rot-dtd-commander/records-dtd
GET https://markdownregistry.com/api/v1/blob/04fc094d01bf8b3585c7d846e8d9bc0812a57b34f3c988563fdb6ab09b4bcd1a

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

ai-slop-dtd SKILL.md skill

nova-violet-role/rot-dtd-commander · skills/ai-slop-dtd/SKILL.md · The AI_SLOP gate, the voice contract of every -dtd answer and, when the Adiutor is armed, of every answer, file, commit…