mcp-fitbit: Instructions file for GitHub Copilot

.github/copilot-instructions.md

mcp-fitbit copilot-instructions.md is an instructions file for GitHub Copilot from TheDigitalNinja/mcp-fitbit. It costs 975 tokens per session, scanned A, original, MIT.

A project guide for an MCP server that connects to Fitbit’s API and returns health data as JSON. JSON is a structured text format commonly used for data exchanged between programs.

In plain words
What is it for?
Developing or checking tools for weight, sleep, exercise, activity, heart rate, and profile data. It also covers building, running, formatting, linting, and authentication.
Why use it?
It gives coding agents the project layout, commands, authentication approach, and rule to mirror Fitbit’s API without changing its data.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is TheDigitalNinja/mcp-fitbit's own configuration. It tells GitHub Copilot how to work on mcp-fitbit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-fitbit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to TheDigitalNinja/mcp-fitbit. 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/TheDigitalNinja/mcp-fitbit/main/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/TheDigitalNinja/mcp-fitbit

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.

agentmods badge for mcp-fitbit copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/thedigitalninja/mcp-fitbit/copilot-instructions.svg)](https://agentmods.dev/instructions/thedigitalninja/mcp-fitbit/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/thedigitalninja/mcp-fitbit/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/thedigitalninja/mcp-fitbit/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>
Per session 975 This file is loaded in full into every session.
When invoked 975 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00975 $0.00975
Opus 5 $0.00487 $0.00487
Sonnet 5 $0.00195 $0.00195
Haiku 4.5 $0.00097 $0.00097

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

Security

Grade A, and why

mcp-fitbit 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 8d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.github/copilot-instructions.md · 76 lines

How it starts

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

GitHub Copilot Instructions

Project Overview

MCP server for Fitbit API integration providing health data access (weight, sleep, activities, profile).

Design Philosophy: This MCP server acts as a 1:1 JSON proxy to the Fitbit API. Tools should match the underlying API parameters and limitations exactly, without adding abstraction layers or client-side data manipulation. Return raw JSON responses from Fitbit API calls.

Development Commands

  • npm run build - Compile TypeScript to build/ directory
  • npm run start - Run the built MCP server
  • npm run dev - Build and run with MCP inspector for testing/debugging
  • npm run lint - Check code quality and style issues
  • npm run format - Auto-fix code formatting
  • npm test - No tests configured yet

Project Structure

  • src/index.ts - Main MCP server entry point, registers all tools
  • src/auth.ts - OAuth2 flow with token persistence
  • src/utils.ts - Shared Fitbit API request utilities
  • src/weight.ts - Weight data tool (time series)
  • src/sleep.ts - Sleep data tool (date range)
  • src/activities.ts - Exercise/activity data tool (date range)
  • src/profile.ts - User profile tool
  • src/heart-rate.ts - Heart rate data tools (time series and date range)
  • src/nutrition.ts - Nutrition data tools (comprehensive food log with macros, plus time series for individual nutrients)
  • build/ - Compiled JavaScript output
  • .env - Environment variables (FITBIT_CLIENT_ID, FITBIT_CLIENT_SECRET)

Code Conventions

  • TypeScript with ES modules
  • Zod for parameter validation
  • All tools return raw JSON from Fitbit API
  • Error handling with console.error for debugging
  • Use makeFitbitRequest utility for API calls
  • API Fidelity: Tool parameters must exactly match Fitbit API requirements - no client-side workarounds or data filtering
  • No Abstraction: If Fitbit API only supports afterDate, the tool should only accept afterDate (not startDate/endDate)
  • Documentation First: Always check the official Fitbit API documentation at https://dev.fitbit.com/build/reference/ when adding new endpoints to ensure proper parameters, authentication scopes, and response formats
  • CRITICAL: Endpoint URL Construction: The makeFitbitRequest utility automatically adds /user/-/ to all endpoint paths. When constructing endpoints, DO NOT include user/-/ in the path - start directly with the resource path (e.g., foods/log/caloriesIn/date/today/1d.json NOT user/-/foods/log/caloriesIn/date/today/1d.json)

Read the full file on GitHub · 76 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.

  1. 8d ago First seen · 76 lines · 975 tokens per session scan A d13c81a87a7e

Subscribe to this mod's changes

mcp-fitbit copilot-instructions.md is an instructions file published in the GitHub repository TheDigitalNinja/mcp-fitbit (33 stars, last pushed 1y ago), licensed MIT. It adds 975 tokens to every session, about $0.0049 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.

Related

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.

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

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

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

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,104 tokens