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/simple10/agents-observe/agents-mdgit clone --depth 1 https://github.com/simple10/agents-observeWhat 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.00835 | $0.00835 |
| Opus 5 | $0.00417 | $0.00417 |
| Sonnet 5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
agents-observe 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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Observe
Real-time observability dashboard for Claude Code agents. Captures every hook event and streams it to a live dashboard.
Install as Plugin
claude plugin marketplace add simple10/agents-observe
claude plugin install agents-observe
Restart Claude Code. The server auto-starts as a Docker container and the dashboard is at http://localhost:4981.
Skills
| Command | Description |
|---|---|
/observe view |
Open the current session in the dashboard |
/observe stats |
Open the current session's stats modal |
/observe |
Open the dashboard |
/observe status |
Server health and config |
/observe start |
Start the server |
/observe stop |
Stop the server |
/observe restart |
Restart the server |
/observe logs |
Show recent container logs |
/observe debug |
Diagnose server issues |
Clone & Run
Requires just, Node.js, and Docker.
git clone https://github.com/simple10/agents-observe.git
cd agents-observe
just install # install dependencies
just start # start server via Docker
Dashboard: http://localhost:4981
For dev mode with hot reload: just dev (client at http://localhost:5174, API at http://localhost:4981).
Troubleshooting
| Problem | Fix |
|---|---|
| Server not running | Run /observe start or restart Claude Code |
| Docker not running | Start Docker Desktop, then /observe start |
| Port conflict | Set AGENTS_OBSERVE_SERVER_PORT=<port> in .env |
| Need diagnostics | Run /observe debug |
| Database issues | Run just db-reset |
Development
Before developing features or modifying code, read docs/DEVELOPMENT.md. It covers architecture, project structure, commands (just dev, just test, etc.), environment variables, worktree setup, code style, and testing.
Key points:
- Use
just devfor hot-reload development - Run
just checkbefore every commit — runs all tests + formatting - Use
justcommands for all dev tasks (notnpmdirectly) — seejust --list - Worktrees need a
.envwith unique ports (see DEVELOPMENT.md § Worktrees) - All env vars are centralized in
hooks/scripts/lib/config.mjs— never readprocess.envelsewhere - TypeScript throughout, kebab-case file names
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.
- 3d ago First seen · 93 lines · 835 tokens per session scan A 3b453d248f16
agents-observe AGENTS.md is an instructions file published in the GitHub repository simple10/agents-observe (664 stars, last pushed 1mo ago), licensed MIT. It adds 835 tokens to every session, about $0.0042 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
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).
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.
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.