abtop is a read-only terminal monitor that shows active Claude Code, Codex CLI, and OpenCode sessions along with token usage, context-window usage, rate limits, child processes, and listening ports. It is for developers running multiple AI coding-agent sessions and needing a view of their local processes and resource limits. The catalogue entries provide instructions for using the monitor.
Borrowing it
Nothing to install: this file belongs to graykode/abtop. 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/graykode/abtop/main/AGENTS.mdgit clone --depth 1 https://github.com/graykode/abtopWrote 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/graykode/abtop/agents-md)<a href="https://agentmods.dev/instructions/graykode/abtop/agents-md"><img src="https://agentmods.dev/badge/instructions/graykode/abtop/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/graykode/abtop/agents-md"><img src="https://agentmods.dev/badge/instructions/graykode/abtop/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.05449 | $0.05449 |
| Opus 5.5 | $0.02180 | $0.02180 |
| Sonnet 5.5 | $0.01090 | $0.01090 |
| Haiku 4.5 | $0.00545 | $0.00545 |
Grade B, and why
abtop AGENTS.md scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`abtop --setup` automates this: creates a script at `~/.claude/abtop-statusline.sh` that writes rate limit JSON to `~/.claude/abtop-rate-limits.json`, and registers it in `~/.claude/settings.json`. How it starts
The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
abtop
AI agent monitor for your terminal. Like btop++, but for AI coding agents.
Supports Claude Code, Codex CLI, and OpenCode sessions.
Language Policy
English is mandatory for all project-facing work and communication.
- Write all source code, comments, tests, fixtures, documentation, examples, configuration text, scripts, and user-facing strings in English.
- Use English for every GitHub artifact: issue titles and bodies, issue comments, pull request titles and descriptions, review comments, commit messages, branch names, release notes, changelogs, discussions, labels, milestones, and workflow or CI messages.
- Do not use non-English text in repository content or GitHub communication unless it is an exact external identifier, a required protocol value, or a direct quote needed for context.
- When quoting or preserving non-English input, add an English explanation and keep the non-English text as short as possible.
- If a contributor opens an issue, comment, or review in another language, respond in English and continue the thread in English.
Architecture
src/
├── main.rs # Entry, terminal setup, event loop, --setup flag
├── app.rs # App state, tick logic, key handling, summary generation
├── setup.rs # StatusLine hook installation (abtop --setup)
├── ui/
│ └── mod.rs # All panels in single file: header, context, quota,
│ # tokens, projects, ports, sessions, footer
├── collector/
│ ├── mod.rs # MultiCollector orchestration, orphan port detection
│ ├── claude.rs # Claude Code: session discovery, transcript parsing
│ ├── codex.rs # Codex CLI: session discovery via ps+lsof, JSONL parsing
│ ├── opencode.rs # OpenCode: session discovery via ps + SQLite DB parsing
│ ├── process.rs # Child process tree (ps) + open ports (lsof) + git stats
│ └── rate_limit.rs # Rate limit file reading (~/.claude/abtop-rate-limits.json)
└── model/
├── mod.rs # Re-exports
└── session.rs # AgentSession, SessionStatus, RateLimitInfo,
# ChildProcess, OrphanPort, SubAgent
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 · 410 lines · 5,449 tokens per session scan B 045975794e89
abtop AGENTS.md is an instructions file published in the GitHub repository graykode/abtop (3,777 stars, last pushed 1mo ago), licensed MIT. It adds 5,449 tokens to every session, about $0.0218 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.