Borrowing it
Nothing to install: this file belongs to jonathan249/health-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/jonathan249/health-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/jonathan249/health-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/jonathan249/health-mcp/agents-md)<a href="https://agentmods.dev/instructions/jonathan249/health-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/jonathan249/health-mcp/agents-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.00589 | $0.00589 |
| Opus 5 | $0.00295 | $0.00295 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
health-mcp AGENTS.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 5d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
server.py is the command-line entry point. It adjusts sys.path before loading
the application from mcp/main.py, where the FastMCP server and transport are
configured. Garmin API access, authentication, response mapping, and caching
live in gateway.py. Tool handlers are registered in mcp/tools.py, while
their dataclass response types are defined in mcp/models.py.
Tests live in tests/ and mirror the main boundaries: test_gateway.py covers
Garmin mapping and caching, and test_server.py checks tool registration.
icon.png is the README asset. Keep mcp/ without an __init__.py; making it
a package would shadow FastMCP's third-party mcp dependency.
Build, Test, and Development Commands
Create an isolated environment and install dependencies:
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
Run all tests with python -m unittest discover -s tests. Start the default
stdio server with python server.py; stdin is reserved for MCP JSON-RPC. For
local HTTP development, run python server.py --transport http, which exposes
http://127.0.0.1:8000/mcp. There is no separate build step or configured
lint/format command.
Coding Style & Naming Conventions
Follow existing Python style: four-space indentation, type annotations,
from __future__ import annotations, and small single-purpose helpers.
Use snake_case for functions and variables, PascalCase for classes and
dataclasses, and leading underscores for private helpers. MCP tool names use
the get_<metric> pattern. Keep imports grouped as standard library,
third-party, then local modules.
Testing Guidelines
Tests use the standard-library unittest framework and should be named
test_*.py, with methods beginning test_. Avoid live Garmin calls: inject a
fake client or gateway, as current tests do. Add focused tests for response
mapping, cache behavior, validation, and registered tool names when changing
those areas.
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.
- 5d ago First seen · 62 lines · 589 tokens per session scan A 9481d8ce0feb
health-mcp AGENTS.md is an instructions file published in the GitHub repository jonathan249/health-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 589 tokens to every session, about $0.0029 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
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.