Borrowing it
Nothing to install: this file belongs to Kepei-Lei102/breakwatch. 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/Kepei-Lei102/breakwatch/main/AGENTS.mdgit clone --depth 1 https://github.com/Kepei-Lei102/breakwatchWrote 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/kepei-lei102/breakwatch/agents-md)<a href="https://agentmods.dev/instructions/kepei-lei102/breakwatch/agents-md"><img src="https://agentmods.dev/badge/instructions/kepei-lei102/breakwatch/agents-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.1 | $0.01374 | $0.01374 |
| Opus 5 | $0.00687 | $0.00687 |
| Sonnet 5 | $0.00275 | $0.00275 |
| Haiku 4.5 | $0.00137 | $0.00137 |
Grade B, and why
breakwatch 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 8d 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.
`~/.claude/settings.json`. **Merge, never overwrite** — that file may already How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent manual — installing and calibrating breakwatch
You have been handed this repository by someone who wants breakwatch set up.
README.md is written for a human deciding whether to install. This file is the
operating procedure for you.
The one thing you can do that a README cannot: calibrate the thresholds to this person before switching anything on. The shipped numbers are one user's, derived from their midnight pattern. Installing them unexamined is the exact mistake this tool exists to correct. Do not skip step 3.
Procedure
0. Check the platform first. macOS is verified end to end. Windows and
Linux are written but were never run — the author had no machine for either.
On those, say so plainly before installing rather than after it fails, and treat
step 5 as a real test rather than a demo. On Windows also confirm the
interpreter: python3 frequently does not resolve there, and if py -3 is what
works, substitute it in both hook commands during install.
1. Install. Ask which they prefer, or infer it — if ~/.claude/plugins/
shows they use plugins, add this repo as a marketplace and
/plugin install breakwatch. Otherwise do the manual install from README.md:
copy plugins/breakwatch/hooks/breakwatch.py to ~/.claude/worklog/, copy
plugins/breakwatch/skills/take-a-break/ to ~/.claude/skills/, copy
HARNESS.md next to the script, and merge the hooks block into
~/.claude/settings.json. Merge, never overwrite — that file may already
hold their permissions, env, and other hooks.
2. Backfill. python3 <path>/breakwatch.py backfill. Claude Code has been
writing timestamped transcripts since they started using it, so this gives them
months of history immediately, and the tool is useful today rather than in a
fortnight. It only writes days that have no file yet, so it is safe to re-run.
3. Calibrate before enabling — the step that matters.
Run report 30 and read it for this person, then say what you found in plain
numbers. Useful questions:
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.
- 8d ago First seen · 104 lines · 1,374 tokens per session scan B 6daf351a9ae6
breakwatch AGENTS.md is an instructions file published in the GitHub repository Kepei-Lei102/breakwatch (1 stars, last pushed 26d ago), licensed MIT. It adds 1,374 tokens to every session, about $0.0069 per session on Opus 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-31.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.