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/mishanefedov/agentwatch/claude-mdgit clone --depth 1 https://github.com/mishanefedov/agentwatchWrote 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/mishanefedov/agentwatch/claude-md)<a href="https://agentmods.dev/instructions/mishanefedov/agentwatch/claude-md"><img src="https://agentmods.dev/badge/instructions/mishanefedov/agentwatch/claude-md.svg" alt="Measured on agentmods" 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 | $0.00112 | $0.00112 |
| Opus 5 | $0.00056 | $0.00056 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
agentwatch CLAUDE.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.
What it actually says
🤖 AI agent in this repo? To use agentwatch (observability across the AI agents on this machine), read AGENTS.md — it self-onboards you in three steps (install → verify → run), no account needed. To contribute, the second half of AGENTS.md has the build/test/typecheck commands and conventions.
This file exists so Claude Code picks up the same context; AGENTS.md is the source of truth.
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 · 8 lines · 112 tokens per session scan A 2b225d1cf5e5
agentwatch CLAUDE.md is an instructions file published in the GitHub repository mishanefedov/agentwatch (14 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session, about $0.0006 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
pad CLAUDE.md
Instructions for PerpetualSoftware/pad, covering pad — development guide, what this is, architecture, build & install and quick iteration loop.
sverklo CLAUDE.md
Instructions for sverklo/sverklo, covering sverklo development, using sverklo tools, project structure and build & test.
brain-os AGENTS.md
Instructions for brainOS-HQ/brain-os, covering agents.md, context, the hard rule, tool routing (in order) and mutation safety.
brain-os copilot-instructions.md
Instructions for brainOS-HQ/brain-os, covering github copilot instructions, read this first, critical rules (also in agents.md) and known bugs (v0.4.1 fixes pending).
brain-os CLAUDE.md
Instructions for brainOS-HQ/brain-os, covering claude.md, agent instructions, build / dev, publish flow and project memory.
code-insights CLAUDE.md
Instructions for melagiri/code-insights, covering claude.md — code insights, project overview, development philosophy (critical), configuration hierarchy and documentation index.