Borrowing it
Nothing to install: this file belongs to kemosabe102/towerwatch-ops-agent. 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/kemosabe102/towerwatch-ops-agent/main/CLAUDE.mdgit clone --depth 1 https://github.com/kemosabe102/towerwatch-ops-agentWrote 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/kemosabe102/towerwatch-ops-agent/claude-md)<a href="https://agentmods.dev/instructions/kemosabe102/towerwatch-ops-agent/claude-md"><img src="https://agentmods.dev/badge/instructions/kemosabe102/towerwatch-ops-agent/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.1 | $0.01655 | $0.01655 |
| Opus 5 | $0.00827 | $0.00827 |
| Sonnet 5 | $0.00331 | $0.00331 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade A, and why
towerwatch-ops-agent 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 7d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Budget: 115 lines / ~1,600 tokens (limit: 150 lines, per
spec-ai-native-repo-layer.md). Measured 2026-07-26. Deep context lives indocs/and loads on demand — this file stays a map, never a manual. Re-measure when you edit it.
Agent-facing guide. The user-facing README is imported below and is the source of truth for the project story, the three-phase map, and the toolchain — read it first, then come back here for the agent-only notes.
@README.md
Repo state — read before reasoning about code
Implementation is partial — check the tree before assuming. The server, config,
domain, and telemetry layers exist, and query_metrics is the only tool built of the
seven in docs/design/. Do not reference, import, or assume the existence of any tool,
module, function, or eval you have not confirmed on disk: the remaining six tools and the
eval suite are still contract-only.
fixtures/stub/ is a stub, not the corpus. Two hand-authored windows proving the
format and the code path. Any number read from it is illustrative, never evidence.
RATIONALE.md records choices that read as defects. Append-only, one
dated entry per deliberate decision a reviewer would otherwise flag. Check it before
reporting a finding, and add an entry when a refuted finding would recur.
What does exist is the contract layer. When asked to build, work from
docs/design/ (the locked tool contracts) and docs/adr/
(the decisions behind them) — not from memory of "what the code probably does," and not
from the Phase 1 spec's candidate tool table, which docs/design/ supersedes.
docs/specs/ is frozen. Never edit a spec to reflect something learned later: the
README's "requirements defined upfront" claim depends on them being unmodified, and a
reader must be able to tell requirement from backfill. Learnings land in docs/design/
(contract) or docs/adr/ (decision), which already win on conflict.
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.
- 7d ago First seen · 125 lines · 1,655 tokens per session scan A 452dade86a4c
towerwatch-ops-agent CLAUDE.md is an instructions file published in the GitHub repository kemosabe102/towerwatch-ops-agent (0 stars, last pushed 16d ago), licensed MIT. It adds 1,655 tokens to every session, about $0.0083 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-31.
Other instructions, from other repositories
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).
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.
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).
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.