Borrowing it
Nothing to install: this file belongs to kamiazya/whiteboard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kamiazya/whiteboard/main/.claude/agents/repo-hygiene-investigator.mdgit clone --depth 1 https://github.com/kamiazya/whiteboardWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/kamiazya/whiteboard/repo-hygiene-investigator)<a href="https://agentmods.dev/agents/kamiazya/whiteboard/repo-hygiene-investigator"><img src="https://agentmods.dev/badge/agents/kamiazya/whiteboard/repo-hygiene-investigator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/kamiazya/whiteboard/repo-hygiene-investigator"><img src="https://agentmods.dev/badge/agents/kamiazya/whiteboard/repo-hygiene-investigator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00094 | $0.00748 |
| Opus 5 | $0.00047 | $0.00374 |
| Sonnet 5 | $0.00019 | $0.00150 |
| Haiku 4.5 | $0.00009 | $0.00075 |
Grade A, and why
repo-hygiene-investigator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
- 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. - 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.
- Evidence over opinion. Every risk must cite concrete evidence: a file path, a
path:line, a grep hit count, agit check-ignoreresult. "It might have secrets" is useless; ".claude/settings.json:21hardcodesAuthorization: Bearer whiteboard-dev, a dev token" is useful. - 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.
- Propose mitigation, not just the problem. For each risk: can it be fixed before adopting (e.g. make path repo-relative, move to
settings.local.json, add a narrower ignore), or is it inherent?
Things worth checking for "track .claude/ in git" specifically
- Secrets / tokens in
settings.json,settings.local.json, MCP server headers, hook commands,.codex/,.agents/. - Machine-specific absolute paths — grep for
/Users/,/home/,$HOME-expanded literals, hardcoded ports, usernames. Workflow scripts that compose via an ABSOLUTEscriptPathare a portability landmine. - Build artifacts / heavy dirs that must stay ignored even if the parent is tracked —
.claude/worktrees/(full checkouts + node_modules), logs, caches, transcripts. - Tool convention — Claude Code's shared-vs-local split (
settings.jsonshareable,settings.local.jsonpersonal/gitignored); whether agents/skills/workflows are meant to be shared. - Local-private intent — content that was deliberately kept off the shared remote (personal context, internal-only agent references, agmsg configs).
- History / churn — would tracking this dir create constant noise (frequently-rewritten local state) in everyone's
git status/diffs.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 34 lines · 94 tokens per session scan A 554ed57a3350
repo-hygiene-investigator is an agent published in the GitHub repository kamiazya/whiteboard (6 stars, last pushed today), licensed Apache-2.0. It adds 94 tokens to every session and 748 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.