repo-hygiene-investigator Claude Code subagentA

repo-hygiene-investigator from kamiazya/whiteboard is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.

Install it, pinned
mdr add kamiazya/whiteboard/.claude/agents/repo-hygiene-investigator.md@git:20260615.5a9e01c

Pins git:20260615.5a9e01c 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/repo-hygiene-investigator.md
Versions recorded
1
Latest version
git:20260615.5a9e01c, committed Jun 15, 2026
Size
3,212 bytes
Repository stars
11
License
Apache-2.0

Lightweight read-only investigator for repo-hygiene / policy / portability questions — e.g. "should we track .claude/ in git", "is it safe to commit this dir", "what breaks for other contributors". Given ONE concern dimension, it inspects the real repo (ignore rules, tracked vs untracked, secrets, machine-specific paths, build artifacts) and returns grounded findings with evidence. Does not edit anything.

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 investigate ONE concern dimension of a repo-hygiene / policy question and report grounded findings. You never edit files; you only read and reason.

## Method

1. **Ground in the real repo.** Use `git` (read-only: `git ls-files`, `git check-ignore -v`, `git status --porcelain`, `git log`, `git grep`), plus Read/Grep/Glob. Never assume — verify against what is actually tracked/ignored/present.
2. **Stay in your dimension.** You are given one angle (e.g. secret-leak, machine-specific-paths, build-artifacts, tooling-convention, contributor-portability, history/churn). Investigate that angle thoroughly; mention cross-cutting issues only as a pointer.
3. **Evidence over opinion.** Every risk must cite concrete evidence: a file path, a `path:line`, a grep hit count, a `git check-ignore` result. "It might have secrets" is useless; "`.claude/settings.json:21` hardcodes `Authorization: Bearer whiteboard-dev`, a dev token" is useful.
4. **Severity honestly.** CRITICAL = secret leak / breaks every other contributor. HIGH = breaks some contributors or leaks machine state. MEDIUM = noise/churn/maintenance burden. LOW = cosmetic. Do not inflate.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add kamiazya/whiteboard/.claude/agents/repo-hygiene-investigator.md@sha256:554ed57a33504a77

The line at the top of this page pins the label git:20260615.5a9e01c, 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 badge

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

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

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in kamiazya/whiteboard/.claude/agents/repo-hygiene-investigator.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 repo-hygiene-investigator.md from somewhere else? Ask it: where did my repo-hygiene-investigator.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 1 version of this file, committed on Jun 15, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260615.5a9e01c latest2026-06-15 5a9e01c 3,212 BA view
Check a whole project

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

A  14 of 14 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Size between 200 bytes and 200 KB (3212 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

kamiazya/whiteboard · 11 stars · license Apache-2.0 · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_mgavtiaiazofytu2
GET https://markdownregistry.com/api/v1/resolve?ref=kamiazya/whiteboard/.claude/agents/repo-hygiene-investigator.md
GET https://markdownregistry.com/api/v1/blob/554ed57a33504a77f28d626f24a3008c894734f15b0e7861bbdbc010801b0106

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

whiteboard-marketplace Plugin marketplace
kamiazya/whiteboard · .claude-plugin/marketplace.json · Claude Code plugin distribution for the @kamiazya/whiteboard collaborative diagramming MCP. (1 plugin: whiteboard)
v0.0.20 · audit A · 11 stars
architect Claude Code subagent
kamiazya/whiteboard · .claude/agents/architect.md · System-design perspective for the plan-initiative panel. Given an initiative + brief, analyzes seams, data model…
git:20260615.5a9e01c · audit A · 11 stars
codebase-auditor Claude Code subagent
kamiazya/whiteboard · .claude/agents/codebase-auditor.md · Read-only whole-codebase health auditor for ONE dimension (wiring-gaps / architecture / maintainability /…
git:20260823.f4de3fa · audit A · 11 stars
developer Claude Code subagent
kamiazya/whiteboard · .claude/agents/developer.md · TDD implementer for one well-scoped change in the whiteboard repo. Spawned by the dev-loop workflow's Implement phase…
git:20261006.53380bb · audit A · 11 stars
dogfood-persona Claude Code subagent
kamiazya/whiteboard · .claude/agents/dogfood-persona.md · Drives the running whiteboard app as a realistic end-user persona via the Playwright MCP browser tools, to surface…
git:20261012.6fa4c18 · audit A · 11 stars
marketing Claude Code subagent
kamiazya/whiteboard · .claude/agents/marketing.md · Drafts release notes, changelog entries, README hero/positioning, and announcements for the whiteboard project…
git:20260615.5a9e01c · audit A · 11 stars
plan-reviewer Claude Code subagent
kamiazya/whiteboard · .claude/agents/plan-reviewer.md · Reviews a draft design/plan for one whiteboard dev task BEFORE implementation, against the repo's completeness rubric…
git:20261002.0803037 · audit A · 11 stars
product-manager Claude Code subagent
kamiazya/whiteboard · .claude/agents/product-manager.md · Product/value perspective for the plan-initiative panel. Given an initiative + brief, clarifies user value, scope vs…
git:20260615.5a9e01c · audit A · 11 stars
project-manager Claude Code subagent
kamiazya/whiteboard · .claude/agents/project-manager.md · Delivery/sequencing perspective for the plan-initiative panel. Given an initiative + brief, slices the work into…
git:20260811.7b616bf · audit A · 11 stars
qa-scenario Claude Code subagent
kamiazya/whiteboard · .claude/agents/qa-scenario.md · QA tester for one specific scenario (startup/docs-reachability/smoke/error-recovery/migration). Spawned by qa to…
git:20261002.0803037 · audit A · 11 stars
research-analyst Claude Code subagent
kamiazya/whiteboard · .claude/agents/research-analyst.md · External-research perspective for the plan-initiative panel. Uses web search/fetch to surface industry best practices…
git:20260615.5a9e01c · audit A · 11 stars
reviewer-dimension Claude Code subagent
kamiazya/whiteboard · .claude/agents/reviewer-dimension.md · Focused code reviewer for one specific review dimension (contract/boundary/dead-code/test-coverage/auth/correctness)…
git:20261013.aa963a1 · audit A · 11 stars

Every file in kamiazya/whiteboard

Browse by kind, by grade A, or by owner.