Borrowing it
Nothing to install: this file belongs to amittamari/hop. 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/amittamari/hop/master/AGENTS.mdgit clone --depth 1 https://github.com/amittamari/hopWrote 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/amittamari/hop/agents-md)<a href="https://agentmods.dev/instructions/amittamari/hop/agents-md"><img src="https://agentmods.dev/badge/instructions/amittamari/hop/agents-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/amittamari/hop/agents-md"><img src="https://agentmods.dev/badge/instructions/amittamari/hop/agents-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.00689 | $0.00689 |
| Opus 5.5 | $0.00276 | $0.00276 |
| Sonnet 5.5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
hop 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Map
This file is the short entry point for coding agents. Keep it small. Durable
project knowledge belongs in docs/.
Start Here
- Project contract:
docs/PROJECT.md - Architecture map:
docs/ARCHITECTURE.md - User-facing usage:
README.md
What This Repo Builds
hop is a Rust CLI/TUI that indexes Claude Code and Codex session JSONL files,
searches them with Tantivy, previews a cleaned transcript, and exec-resumes the
selected session in the original working directory.
Working Rules
- Read
docs/RUST_GUIDELINES.mdbefore starting any implementation work. - Prefer the existing module boundaries over introducing new framework shape.
- Prefer files under ~500 lines. Crossing it on a file you're editing is a signal
to split by responsibility — not a hard limit. If a file is legitimately over
(e.g. dominated by colocated
#[cfg(test)]tests), add a one-line note near the top explaining why, and move on. Don't split modules purely to satisfy the count. - Keep
main.rsas orchestration only when possible; reusable behavior belongs in library modules. - Parse external data at adapter boundaries into
coretypes before indexing or rendering. - Keep agent-specific knowledge inside its adapter (
B-011): format quirks, magic field values, and per-agent judgments belong inadapters/<agent>.rs. Generic layers (engine,core,index,tui) must not name an agent-specific literal oradapters::<agent>::…symbol — reach adapters only through theAdaptertrait. When a generic layer needs a per-agent decision, add an agent-agnostic trait method with a safe default and override it in the adapter. - Keep the TUI responsive: no network calls, large scans, or broad filesystem work in the render path.
- Preserve resume behavior: restore the terminal before
exec, thenchdirand replace the process with the agent CLI. - Update documentation when changing architecture, user-visible behavior, or agent-facing workflows.
- Never write absolute local working-directory paths (e.g.
/Users/<name>/...or a personal~/workspaces/...layout) into committed files. Reference repos and files by their repo-relative path, well-known data dirs (~/.codex,~/.claude), or a neutral description like "a local checkout".
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.
- 1mo ago First seen · 66 lines · 689 tokens per session scan A 13f44de242a7
hop AGENTS.md is an instructions file published in the GitHub repository amittamari/hop (5 stars, last pushed 11d ago), licensed MIT. It adds 689 tokens to every session, about $0.0028 per session on Opus 5.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 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.