Borrowing it
Nothing to install: this file belongs to bearlike/Grove. 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/bearlike/Grove/current/CLAUDE.mdgit clone --depth 1 https://github.com/bearlike/GroveWrote 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/bearlike/grove/claude-md)<a href="https://agentmods.dev/instructions/bearlike/grove/claude-md"><img src="https://agentmods.dev/badge/instructions/bearlike/grove/claude-md/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/instructions/bearlike/grove/claude-md"><img src="https://agentmods.dev/badge/instructions/bearlike/grove/claude-md.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.09317 | $0.09317 |
| Opus 5.5 | $0.03727 | $0.03727 |
| Sonnet 5.5 | $0.01863 | $0.01863 |
| Haiku 4.5 | $0.00932 | $0.00932 |
Grade D, and why
Grove CLAUDE.md scanned grade D with 3 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 18d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Never run a Grove entrypoint as root — it poisons the editable install, and uv's error never says so.** The `uv tool` venv and (editable install ⇒) the checkout's `src/grove/**/__pycache__` are user-owned; one root-r Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
- **A Grove workspace is a git worktree, so it sees only committed files.** Uncommitted working-tree edits never propagate into a worktree — commit shared config (e.g. `.mcp.json`, whose tokens are env refs, not literals Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Never run a Grove entrypoint as root — it poisons the editable install, and uv's error never says so.** The `uv tool` venv and (editable install ⇒) the checkout's `src/grove/**/__pycache__` are user-owned; one root-r How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grove — Agent Guide
Grove lets you tend multiple git worktrees like branches in a forest: spin up, switch between, and tear down isolated coding sessions without losing your place. See README.md for the product brief.
Handling a handed-off issue (the autonomous workspace loop)
When you own a tracker issue end-to-end, drive it to a merged PR on this loop. Bias to action — never over-plan, over-spec, ask trivial questions, or invent fallbacks nobody requested.
- Read the issue, map the components, implement. Read the nearest owning
CLAUDE.md(s) on the path you'll touch before editing. - The PR BODY must end with one
Closes #<n>line per issue it resolves; the PR TITLE carries no issue number. Gitea only auto-closes on the literal closing keyword (close/closes/fixes) followed by#<n>— a body that merely mentions the number, or a comment on the issue naming the PR, closes nothing, and that gap left 100+ issues open behind merged PRs. The split is by artifact, and the honest reason is narrower than it looks: the squash title inherits the PR title and mirrors to the public GitHub remote, where a bare#<n>resolves against a different tracker, so the title stays a clean gitmoji/conventional summary. The body is NOT Gitea-only — measured 2026-09-13, Gitea's squash commit carries the PR body verbatim,Reviewed-on:URL and issue-ops footer included, so it reaches the mirror too. That is fine (those host URLs are already on every existing commit and aClosesline adds nothing new), but do not justify this rule with "the body never leaves Gitea", because the next person will check. - Check the open PR for conflicts with the remote target and resolve them — rebase onto the freshly-fetched target, re-apply onto the current structure (don't clobber what landed meanwhile), re-run the gates, force-push.
- Reply on the issue naming the PR. Summarize the design decision, the components touched, and the gate results. Say plainly anything that did not work, anything left out, and any acceptance criterion that turned out to be unsatisfiable — a ticket whose own premise was wrong is the most valuable thing you can leave behind, and the next session cannot recover it from the diff. Do not close the issue by hand — the keyword closes it at merge, which is the right moment — but after the merge, verify it actually closed rather than assuming the keyword did its job; an open ticket with a linked PR is honest, a closed one with unmerged work is not.
- After implementing, fold the durable insights into the nearest owning
CLAUDE.md— the invariant, the trade-off, the reference you'd otherwise re-derive; never copyable snippets or restatements of code.
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.
- 18d ago Changed · -10 tokens per session 58c8fce62577
- 26d ago Changed · +6 lines · +774 tokens per session 85b25b33f3ca
- 1mo ago Changed · +13 lines · +2,556 tokens per session ed2955d77ad9
- 1mo ago First seen · 130 lines · 5,997 tokens per session scan D ee78375f7fa0
Grove CLAUDE.md is an instructions file published in the GitHub repository bearlike/Grove (9 stars, last pushed 18d ago), licensed MIT. It adds 9,317 tokens to every session, about $0.0373 per session on Opus 5.5. A static security scan graded it D with 3 findings (asks for root, reads mcp configuration, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.