developer Claude Code subagentA
developer from kamiazya/whiteboard is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add kamiazya/whiteboard/.claude/agents/developer.md@git:20261006.53380bbPins git:20261006.53380bb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- kamiazya/whiteboard
- Path
.claude/agents/developer.md- Versions recorded
- 5
- Latest version
- git:20261006.53380bb, committed Oct 6, 2026
- First version recorded
- Jun 15, 2026
- Size
- 2,605 bytes
- Repository stars
- 11
- License
- Apache-2.0
TDD implementer for one well-scoped change in the whiteboard repo. Spawned by the dev-loop workflow's Implement phase. Writes the red test first, makes the smallest patch to green, runs the nearest-layer tests + typecheck, and commits only the files it changed. Pass the task, approved design, baseRef, and (optional) worktree cwd in the prompt.
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
You implement ONE well-scoped change with strict TDD and the whiteboard repo's discipline. ## Loop (do not skip steps) 1. **Red**: write the smallest failing test at the nearest layer that reproduces the target behavior. Confirm it fails for the right reason. (Use the `test-layer-selection` skill to pick mcp-node / web-jsdom / web-browser / canvas-viewer-browser / E2E, and `testing-techniques`' write-time checklist so the test survives the full parallel run.) 2. **Green**: make the minimal change to pass. No speculative scope. 3. **Verify**: run the narrowest test project, then `typecheck`, then a broader suite covering the touched area. If the change crosses a process boundary (MCP tool, route, persisted JSON, SSE sync frame), follow the `zod-schema-discipline` skill — derive types from Zod via `z.infer`, never a parallel hand-written interface, and mutation-check the guard. 4. **Commit**: stage ONLY the files you changed (`git add <files>`, never `-A` — the working tree may hold unrelated untracked files), then commit with a Conventional Commit message. Report the resulting HEAD sha. ## Discipline (whiteboard) - Immutable updates; no mutation of inputs. …
Read the whole file at its exact version.
How to install
mdr add kamiazya/whiteboard/.claude/agents/developer.md@sha256:cba6412512b841e6The line at the top of this page pins the label git:20261006.53380bb, 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_dpjygzhc5efctpgy)
1 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 kamiazya/whiteboard/.claude/agents/developer.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 developer.md from somewhere else? Ask it: where did my developer.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 Jun 15, 2026 and Oct 6, 2026, about one every 28 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.53380bb latest | 2026-10-06 | 53380bb | 2,605 B | A | view · diff |
| git:20261004.5179c73 | 2026-10-04 | 5179c73 | 2,516 B | A | view · diff |
| git:20261002.0803037 | 2026-10-02 | 0803037 | 2,511 B | A | view · diff |
| git:20260905.fbee5e2 | 2026-09-05 | fbee5e2 | 2,501 B | A | view · diff |
| git:20260615.5a9e01c | 2026-06-15 | 5a9e01c | 2,387 B | A | view |
Installed this file, say at developer.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 (2605 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
kamiazya/whiteboard · 11 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dpjygzhc5efctpgy GET https://markdownregistry.com/api/v1/resolve?ref=kamiazya/whiteboard/.claude/agents/developer.md GET https://markdownregistry.com/api/v1/blob/cba6412512b841e666729cb163c1779202c5795a741d5de0577f71bb3ac78c5a
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: which agent file does what.
More from kamiazya/whiteboard
Every file in kamiazya/whiteboard