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/ntppool/monitor/claude-mdgit clone --depth 1 https://github.com/ntppool/monitorWhat 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.05632 | $0.05632 |
| Opus 5 | $0.02816 | $0.02816 |
| Sonnet 5 | $0.01126 | $0.01126 |
| Haiku 4.5 | $0.00563 | $0.00563 |
Grade A, and why
monitor 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 2d 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 — 615 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM_CODING_AGENT.md
This file provides guidance to Claude Code (claude.ai/code) and other LLM-based coding agents when working with code in this repository.
Project Overview
The NTP Pool Monitor is a distributed monitoring system for the NTP Pool project. It consists of three main components:
ntppool-agent- Monitoring client that runs on distributed nodesmonitor-api- Central API server for coordination and configurationmonitor-scorer- Processes monitoring results and calculates server scores
Task Management
Use TodoWrite/TodoRead tools for complex multi-step tasks (3+ steps) or when user explicitly requests todo management.
Best Practices:
- Break down complex tasks into specific, actionable items
- Mark tasks
in_progressbefore starting work (only ONE at a time) - Complete tasks immediately after finishing
- Only mark
completedwhen fully accomplished
Pre-Commit Checklist
MANDATORY before any git commit:
- Run
gofumpt -won all changed.gofiles - Run
make testto ensure all tests pass - Verify compilation with
go buildfor affected packages - Run lint tools if available (
golangci-lint run,go vet ./...) - Check for race conditions and proper error handling
Never commit changes unless explicitly asked by the user.
NEVER USE git add -A - always use explicit, targeted git staging.
Development Commands
make tools # Install required development tools
make generate # Generate all code (runs sqlc then go generate ./...)
make build # Build all components
make test # Run comprehensive test suite
Code Generation
Never edit generated files directly - changes will be lost on regeneration.
Generated file patterns:
*.pb.go- Protocol buffer generated files*.sql.go- sqlc generated database codeotel.go- OpenTelemetry instrumentation wrappers*_string.go- Enum string methods- Files in
api/pb/andgen/directories
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.
- 2d ago First seen · 615 lines · 5,632 tokens per session scan A 48ab3869e86d
monitor CLAUDE.md is an instructions file published in the GitHub repository ntppool/monitor (20 stars, last pushed 3mo ago), licensed MIT. It adds 5,632 tokens to every session, about $0.0282 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
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.