Borrowing it
Nothing to install: this file belongs to loganmurphy/oura-mcp-server. 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/loganmurphy/oura-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/loganmurphy/oura-mcp-serverWrote 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/loganmurphy/oura-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/loganmurphy/oura-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/loganmurphy/oura-mcp-server/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.02391 | $0.02391 |
| Opus 5 | $0.01196 | $0.01196 |
| Sonnet 5 | $0.00478 | $0.00478 |
| Haiku 4.5 | $0.00239 | $0.00239 |
Grade A, and why
oura-mcp-server CLAUDE.md scanned grade A 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `?no_cache` query param on the endpoint URL — per-request; useful for `curl` smoke tests How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Commands
pnpm dev # Start local dev server on http://localhost:8787 (Miniflare, hot reload)
pnpm deploy # Deploy to Cloudflare Workers (requires wrangler login)
pnpm cf-typegen # Regenerate worker-configuration.d.ts from wrangler.jsonc bindings
pnpm bootstrap # Interactive wizard — provisions D1, KV, deploys Worker, copies MCP URL to clipboard
pnpm connect-local # Set up local credentials + D1 schema (no Cloudflare needed)
pnpm revoke # Invalidate all active OAuth sessions in KV (Claude re-auths on next use)
pnpm reset # Clear .dev.vars + .bootstrap-state + wrangler.jsonc (local state only, does not touch KV)
pnpm format # Prettier (write)
pnpm format:check # Prettier (check only — used by pre-commit hook)
pnpm lint # oxlint (typescript/no-explicit-any + recommended rules, --deny-warnings)
pnpm test # Vitest unit tests
pnpm coverage # Vitest + v8 coverage (≥90% threshold)
npx tsc --noEmit -p tsconfig.scripts.json # Type-check the bootstrap script
npx tsc --noEmit # Type-check the Worker (no build step — wrangler bundles via esbuild)
Code style
Prettier enforces formatting on every commit (pnpm format:check runs in the pre-commit hook). Config: no semis, trailing commas, 100-char print width. Run pnpm format to auto-fix before committing.
- No section-header comments (
// ── Foo ────). Comments only where behavior is non-obvious.
Pre-commit hooks are managed by lefthook (lefthook.yml). They install automatically on pnpm install and run lint + both typechecks in parallel before every commit. To run manually: pnpm lefthook run pre-commit.
D1 migrations:
npx wrangler d1 execute oura-cache --local --file=./migrations/001_init.sql # local
npx wrangler d1 execute oura-cache --remote --file=./migrations/001_init.sql # production
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.
- 6d ago First seen · 151 lines · 2,391 tokens per session scan A 83e2691e2a86
oura-mcp-server CLAUDE.md is an instructions file published in the GitHub repository loganmurphy/oura-mcp-server (2 stars, last pushed 4mo ago), licensed MIT. It adds 2,391 tokens to every session, about $0.0120 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.