What is whoop-mcp copilot-instructions.md?

Project instructions for a TypeScript server that lets AI assistants access WHOOP health and fitness data through the WHOOP REST API. They describe its tools, code style, commands, and testing approach.

Use them when adding or changing WHOOP API tools, editing TypeScript files, running the build, linting, type checks, or writing Vitest tests.

They give a coding agent the project-specific rules needed to make consistent changes and check that the server still works. They also explain test-driven development (writing tests before code) and the required checks.

How shashankswe2020-ux/whoop-mcp configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to shashankswe2020-ux/whoop-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.

Copy the file

curl -O https://raw.githubusercontent.com/shashankswe2020-ux/whoop-mcp/main/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/shashankswe2020-ux/whoop-mcp

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/shashankswe2020-ux/whoop-mcp/copilot-instructions/github.svg)](https://agentmods.dev/instructions/shashankswe2020-ux/whoop-mcp/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/shashankswe2020-ux/whoop-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/shashankswe2020-ux/whoop-mcp/copilot-instructions/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/shashankswe2020-ux/whoop-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/shashankswe2020-ux/whoop-mcp/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 806 This file is loaded in full into every session.

When invoked 806 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00806	$0.00806
Opus 5	$0.00403	$0.00403
Sonnet 5	$0.00161	$0.00161
Haiku 4.5	$0.00081	$0.00081

Measured 12d ago against content hash c5cbf3379de5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

whoop-mcp copilot-instructions.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.

.github/copilot-instructions.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project: whoop-mcp

An MCP server wrapping the WHOOP REST API for AI assistant access to health/fitness data.

Tech Stack

TypeScript ~5.x (strict, no any), Node.js >= 18, native fetch
@modelcontextprotocol/sdk, Zod, Vitest, ESLint, Prettier
Build: tsc — no bundler. No runtime deps beyond SDK + Zod.

Commands

npm run build       # Build TypeScript
npm test            # Run tests (Vitest)
npm run lint        # ESLint
npm run lint:fix    # ESLint + fix
npm run format      # Prettier
npm run typecheck   # tsc --noEmit
npm run dev         # Dev mode (tsx)

Code Conventions

Files: kebab-case.ts | Types: PascalCase | Functions: camelCase | Constants: SCREAMING_SNAKE_CASE
MCP tool names: snake_case (MCP convention)
Named exports only (no default exports)
Explicit return types on all exported functions
One tool per file — handler + Zod schema co-located
Errors throw typed errors, never return error codes
Tests mirror src/ structure in tests/ directory

Testing

Write tests before code (TDD)
For bugs: write a failing test first, then fix (Prove-It pattern)
Test hierarchy: unit > integration > e2e (use the lowest level that captures the behavior)
Mock the WHOOP API — never hit real API in tests. Use vi.fn() for fetch.
Coverage target: >80% on src/auth/ and src/api/, >70% overall
Run npm test after every change

Code Quality

Review across five axes: correctness, readability, architecture, security, performance
Every PR must pass: lint, type check, tests, build
No secrets in code or version control

Implementation

Build in small, verifiable increments
Each increment: implement → test → verify → commit
Never mix formatting changes with behavior changes

Key References

Spec: docs/specs/whoop-mcp-server.md
Implementation plan: docs/specs/implementation-plan.md
Code review: docs/reviews/code-review-checkpoint-1.md (Tasks 1–5 approved)
WHOOP API base: https://api.prod.whoop.com/developer (v2 endpoints)
OAuth: Authorization Code flow, tokens at ~/.whoop-mcp/tokens.json (0600 perms)

Read the full file on GitHub · 66 lines

Changes

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 · 66 lines · 806 tokens per session scan A c5cbf3379de5

Subscribe to this mod's changes

whoop-mcp copilot-instructions.md is an instructions file published in the GitHub repository shashankswe2020-ux/whoop-mcp (153 stars, last pushed yesterday), licensed MIT. It adds 806 tokens to every session, about $0.0040 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.

agentskills fitness-tracker mcp-server npm-package whoop-api

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.

github/spec-kit · 7,126 tokens

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

whoop-mcp: Instructions file for GitHub Copilot