AGENTS.md@claude/dev-mods/tool-historyA
AGENTS.md@claude/dev-mods/tool-history from ronnasayd/aipp is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add ronnasayd/aipp/claude/dev-mods/tool-history/AGENTS.md@git:20261105.4ba4217Pins git:20261105.4ba4217 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- ronnasayd/aipp
- Path
claude/dev-mods/tool-history/AGENTS.md- Versions recorded
- 5
- Latest version
- git:20261105.4ba4217, committed Nov 5, 2026
- First version recorded
- Oct 29, 2026
- Size
- 2,806 bytes
- Repository stars
- 3
- License
- none declared
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
# tool-history
## Card spacing
- Cards in the pane (tool calls and agent messages) sit flush: the `list` Box
in `hooks/register.tsx` uses `gap={0}`. No blank line between cards — the
round border already separates them.
- Do not add `gap`, `marginY`, `marginTop` or `marginBottom` to the `list` Box
or to individual cards. `tests/collapse.test.tsx` asserts `gap` is `0`.
- Why: when cards were grouped per agent, `gap={1}` only separated groups.
After the groups were flattened (each card names its agent), the same
`gap={1}` landed between every card and the pane got sparse.
## Border colors
- Yellow border = subagent, and only in the messages tab (agent message cards).
- Tool call cards (Bash, Read, etc.) never use yellow, even when a subagent
made the call: `danger` on error, `subtle` when done, `claude` while running.
`tests/subagent-border.test.tsx` asserts this.
## Agent tool calls in the messages tab
- Each `Agent` tool call also adds a `kind: "agent"` card to the messages tab
(key `agent-call-<tool_use_id>`): `subagent_type`, `description` and the
full `prompt`. Border follows the caller (yellow only if a subagent spawned
…Read the whole file at its exact version.
How to install
mdr add ronnasayd/aipp/claude/dev-mods/tool-history/AGENTS.md@sha256:3e3b3c258bf78630The line at the top of this page pins the label git:20261105.4ba4217, 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_tp6s23pxkutz3wah)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in ronnasayd/aipp/claude/dev-mods/tool-history/AGENTS.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of AGENTS.md from somewhere else? Ask it: where did my AGENTS.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Oct 29, 2026 and Nov 5, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261105.4ba4217 latest | 2026-11-05 | 4ba4217 | 2,806 B | A | view · diff |
| git:20261104.2e80376 | 2026-11-04 | 2e80376 | 2,805 B | A | view · diff |
| git:20261103.224a30c | 2026-11-03 | 224a30c | 2,111 B | A | view · diff |
| git:20261029.fde17f9 | 2026-10-29 | fde17f9 | 1,605 B | A | view · diff |
| git:20261029.2e3b9b1 | 2026-10-29 | 2e3b9b1 | 1,225 B | A | view |
Installed this file, say at AGENTS.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (2806 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
ronnasayd/aipp · 3 stars · license none declared · pushed 2026-11-18 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_tp6s23pxkutz3wah GET https://markdownregistry.com/api/v1/resolve?ref=ronnasayd/aipp/claude/dev-mods/tool-history/AGENTS.md GET https://markdownregistry.com/api/v1/blob/3e3b3c258bf78630cbe73aec6a067695ce50e85dea07240daaaeb29fd8f78db1
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: how to write a good AGENTS.md · AGENTS.md vs CLAUDE.md · which agent file does what.