Home / rjmurillo / ai-agents · GitHub

ai-agents-docs-of-record SKILL.md skillA

ai-agents-docs-of-record from rjmurillo/ai-agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add rjmurillo/ai-agents/ai-agents-docs-of-record@v1.0.0

Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: rjmurillo/ai-agents
Path: .claude/skills/ai-agents-docs-of-record/SKILL.md
Versions recorded: 5
Latest version: v1.0.0, committed Sep 25, 2026
First version recorded: Sep 12, 2026
Size: 18,348 bytes
Repository stars: 48
License: MIT

Runbook for this repo's documents of record. Session logs, ADRs, retrospectives, Serena memories, per-issue handoffs, plus the templates, validators, naming rules, and house prose style that bind them. Use when you say `write the session log`, `create an ADR`, `fill the retro`, `save this to memory`, `which document of record`. Do NOT use for authoring skills (use `SkillForge`) or research write-ups (use `ai-agents-research-methodology`).

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

# ai-agents-docs-of-record

<!-- vendor-portability: contributor-facing knowledge pack for the rjmurillo/ai-agents repo itself; intentionally references upstream paths (.agents/, .claude/, scripts/, build/) because its audience is repo contributors, not plugin consumers (issue #2050) -->
This repo runs on verification-based governance. Continuity lives in per-issue
handoffs and Serena memory. Session log creation is discontinued; transcript
and pull request evidence remain valid, and the ~1,500 historical logs under
`.project-toolkit/sessions/` stay in the repo as history.

## Triggers

- `write the session log`
- `create an ADR`
- `fill the retro`
- `save this to memory`
- `which document of record does this go in`

## The Record System Map

| Record | Location | Create with | Validated by |
|--------|----------|-------------|--------------|
| Session log (historical only, creation discontinued) | `.project-toolkit/sessions/YYYY-MM-DD-session-NN[-slug].json` | do not create new ones | `scripts/validate_session_json.py`, validate-if-present via the `session-policy` pre-commit hook, applies only if one is somehow staged |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add rjmurillo/ai-agents/ai-agents-docs-of-record@sha256:5a8737db8ac2b1d9

The line at the top of this page pins the label v1.0.0, 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_zrliij2eaai5tsz6.svg)](https://markdownregistry.com/a/art_zrliij2eaai5tsz6)

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

Versions

The registry has recorded 5 versions of this file, between Sep 12, 2026 and Sep 25, 2026, about one every 3 days.

version	committed	commit	size	audit
v1.0.0 latest	2026-09-25	3fda96c	18,348 B	A	view · diff
v1.0.0	2026-09-23	efd148e	18,137 B	A	view · diff
v1.0.0	2026-09-19	49d28a5	17,903 B	A	view · diff
v1.0.0	2026-09-16	659097d	17,972 B	A	view · diff
v1.0.0	2026-09-12	1335030	17,844 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 (18348 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

rjmurillo/ai-agents · 48 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_zrliij2eaai5tsz6
GET https://markdownregistry.com/api/v1/resolve?ref=rjmurillo/ai-agents/ai-agents-docs-of-record
GET https://markdownregistry.com/api/v1/blob/5a8737db8ac2b1d9993541a91b3de15d6423c5b570836058c6188356a8905528

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.