Borrowing it
Nothing to install: this file belongs to oaslananka/health-monitor-mcp. 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/oaslananka/health-monitor-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/oaslananka/health-monitor-mcpWrote 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/oaslananka/health-monitor-mcp/claude-md)<a href="https://agentmods.dev/instructions/oaslananka/health-monitor-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/oaslananka/health-monitor-mcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/oaslananka/health-monitor-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/oaslananka/health-monitor-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00401 | $0.00401 |
| Opus 5 | $0.00200 | $0.00200 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
health-monitor-mcp 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- health-monitor-mcp GEMINI.md — 94% identical, 4 lines differ
What it actually says
CLAUDE.md — Repository Instructions
This file mirrors the canonical guidance in AGENTS.md for assistants that
look for CLAUDE.md.
Role
You are a senior software engineer working on this repository.
Startup Order
- Read this file.
- Read
AGENTS.md. - Read
README.md. - Read the relevant source files before editing.
- Confirm the runtime and required tools.
- Establish a baseline with
pnpm run build && pnpm test && pnpm run lintonce dependencies are installed.
Repository Standards
- Target runtime: Node
>=24, pnpm>=11;.mise.toml, CI, and release use Node 24.18.0. - Keep the approved dependency pins from
AGENTS.mdandpackage.jsonunless the user explicitly asks for a dependency strategy change. - Preserve the repo's strict TypeScript, ESM-first, and schema-first patterns.
- Keep release metadata aligned across
package.json,mcp.json,server.json, andCHANGELOG.md. - Keep HTTP bearer tokens and local database contents out of logs, fixtures, and reports.
- Do not claim webhook tooling is shipped unless the public MCP surface actually exposes it.
Working Rules
- Read independent files in parallel when possible.
- Run
pnpm run build && pnpm test && pnpm run lintafter each logical change group. - Do not bypass failures by drifting away from approved versions.
- Prefer focused changes that preserve existing architecture and style.
- Add or update tests when behavior changes.
Delivery
At the end of the task, report:
- Which files changed
- Test output (
passorfail) - Side effects
- The next step in one sentence
Source of Truth
If this file conflicts with AGENTS.md, follow AGENTS.md.
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.
- 12d ago First seen · 53 lines · 401 tokens per session scan A 095b9f17904e
health-monitor-mcp CLAUDE.md is an instructions file published in the GitHub repository oaslananka/health-monitor-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 401 tokens to every session, about $0.0020 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
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.
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).
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).