Borrowing it
Nothing to install: this file belongs to wenhanweime/herdr-plugin-renamer. 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/wenhanweime/herdr-plugin-renamer/main/CLAUDE.mdgit clone --depth 1 https://github.com/wenhanweime/herdr-plugin-renamerWrote 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/instructions/wenhanweime/herdr-plugin-renamer/claude-md)<a href="https://agentmods.dev/instructions/wenhanweime/herdr-plugin-renamer/claude-md"><img src="https://agentmods.dev/badge/instructions/wenhanweime/herdr-plugin-renamer/claude-md.svg" alt="Measured on agentmods" 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.03319 | $0.03319 |
| Opus 5 | $0.01659 | $0.01659 |
| Sonnet 5 | $0.00664 | $0.00664 |
| Haiku 4.5 | $0.00332 | $0.00332 |
Grade A, and why
herdr-plugin-renamer CLAUDE.md 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 8d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
herdr plugin (Rust) that names a herdr pane from the coding agent's first prompt. When the pane is in an auto-generated linked worktree, it also renames the worktree branch and workspace. The naming engine is swappable. The default chain uses headless Pi first and then free OpenCode models; Apple FoundationModels, Codex, and Claude remain explicit engine selections.
Architecture
Single binary, two phases (src/main.rs):
- Hot phase (default, every
pane.agent_status_changedevent): pure env-var reads, no I/O.context::evaluatebails unless the new status isworkingand this pane does not already have a done marker. On a pass, writes a pane-scoped claim marker and forks the cold phase detached (setsid). - Cold phase (
HERDR_NAMING_PHASE=cold):herdr::poll_agent_session→transcript::read_first_prompt→main::generate_name(walks theengine::engine_chain; fallbacksslug::display_fallbackfor labels andslug::fallback_from_promptfor branch slugs) → renames configured targets. The generated name is also reported as thetaskmetadata token on the pane and workspace for custom Agent and Space sidebar rows. With the defaulttabtarget on a non-linked workspace, the title is written toworkspace(herdr 0.7.4's only bright Agent-sidebar token) and the tab gets the cwd folder basename (dim). Linked worktrees skip that title-on-workspace step so the later branch-slug rename can own the label. Multi-tab siblings share one workspace label (last writer wins). If the pane is in a linked worktree whose current branch starts withworktree/,git::rename_current_branchrenames it to<prefix>/<slug>and only thenherdr::workspace_renamerenames the workspace to<slug>.
Naming outputs: title on workspace (non-worktree); folder on tab; optional
pane/agent renames via targets; $task metadata always. Branch
<prefix>/<slug> (bare <slug> when no prefix); workspace <slug> after a
successful worktree branch rename. The prefix comes from
main::resolve_branch_prefix: HERDR_NAMING_BRANCH_PREFIX env, then a
branch-prefix file in HERDR_PLUGIN_CONFIG_DIR, else none.
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.
- 8d ago First seen · 224 lines · 3,319 tokens per session scan A 026bc60029b3
herdr-plugin-renamer CLAUDE.md is an instructions file published in the GitHub repository wenhanweime/herdr-plugin-renamer (16 stars, last pushed 27d ago), licensed MIT. It adds 3,319 tokens to every session, about $0.0166 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-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.