Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/ziims/grove/agents-mdgit clone --depth 1 https://github.com/ZiiMs/GroveWhat 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 | $0.02477 | $0.02477 |
| Opus 5 | $0.01239 | $0.01239 |
| Sonnet 5 | $0.00495 | $0.00495 |
| Haiku 4.5 | $0.00248 | $0.00248 |
Grade A, and why
Grove AGENTS.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 2d 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidelines for coding agents working in the Grove codebase.
Project Overview
Grove is a terminal UI (TUI) for managing multiple Claude Code agents with git worktree isolation. Built with Rust using ratatui for the UI, tokio for async runtime, and git2 for git operations.
Build/Lint/Test Commands
cargo build # Development build
cargo build --release # Production build
cargo test # Run all tests
cargo test test_name # Run a single test by name
cargo test -- --nocapture # Run tests with output visible
cargo clippy --all-targets --all-features -- -D warnings # Lint
cargo fmt -- --check # Format check
cargo fmt # Auto-format
cargo run -- /path/to/repo # Run the application
Code Style Guidelines
Error Handling
Use anyhow for error handling:
use anyhow::{Context, Result, bail};
fn load_config() -> Result<Config> {
let content = std::fs::read_to_string(&path)
.context("Failed to read config file")?;
Ok(toml::from_str(&content).context("Failed to parse config")?)
}
Async Patterns
#[tokio::main]
async fn main() -> Result<()> { /* ... */ }
let (action_tx, mut action_rx) = mpsc::unbounded_channel::<Action>();
tokio::spawn(async move { let _ = tx.send(Action::UpdateStatus { ... }); });
Module Organization
Each module has a mod.rs that re-exports public items:
// src/agent/mod.rs
pub mod detector;
pub mod manager;
pub mod model;
pub use detector::detect_status;
pub use manager::AgentManager;
pub use model::{Agent, AgentStatus};
Naming Conventions
- Functions/variables:
snake_case(select_next,agent_list) - Types/traits:
PascalCase(AppState,AgentStatus) - Constants:
SCREAMING_SNAKE_CASE(MAX_BUFFER_SIZE)
Serde Patterns
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct Config {
#[serde(default)]
pub gitlab: GitLabConfig,
#[serde(skip)]
pub git_status: Option<GitSyncStatus>, // Runtime-only
}
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.
- 2d ago First seen · 368 lines · 2,477 tokens per session scan A 683aba216176
Grove AGENTS.md is an instructions file published in the GitHub repository ZiiMs/Grove (23 stars, last pushed 6mo ago), licensed MIT. It adds 2,477 tokens to every session, about $0.0124 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
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.
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).
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.