Borrowing it
Nothing to install: this file belongs to jhoy1020/garmin-coach-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/jhoy1020/garmin-coach-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/jhoy1020/garmin-coach-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/jhoy1020/garmin-coach-mcp/claude-md)<a href="https://agentmods.dev/instructions/jhoy1020/garmin-coach-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/jhoy1020/garmin-coach-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/jhoy1020/garmin-coach-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/jhoy1020/garmin-coach-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.01673 | $0.01673 |
| Opus 5 | $0.00837 | $0.00837 |
| Sonnet 5 | $0.00335 | $0.00335 |
| Haiku 4.5 | $0.00167 | $0.00167 |
Grade A, and why
garmin-coach-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 10d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
garmin-coach-mcp — context for agents
An MCP server exposing one person's Garmin Connect data as tools. Runs locally over stdio, or hosted on Azure Container Apps behind Microsoft Entra sign-in.
If someone is setting this up, ask which they want — local takes about two minutes, hosted takes about twenty and costs ~$5/month.
THIS REPOSITORY IS PUBLIC
Read this section before writing to any tracked file.
Never commit any of these. They are not credentials, but they identify the author and are useless to a reader:
- a path containing a real username —
C:\Users\<name>,/home/<name> - an absolute path into someone's checkout — derive from
repo_root()instead - a real resource-group name, an Azure region inside a command, or a Container Apps FQDN
- a tenant, subscription, client or object GUID
- an email address, or a real credential expiry date
Use <placeholder> in docs, and derive at runtime in code. python scripts/check_secrets.py
enforces this and runs as a pre-commit hook; CI runs it too. A justified exception uses
a per-line # check-secrets: allow personal pragma, never a file-wide allowlist.
Secrets live in exactly two places, both gitignored: .azure/<env>/.env and
~/.garminconnect. Nothing else. Do not create a third.
Never print secrets into the conversation. In particular, do not run
azd env get-values — it prints three live credentials. Use python scripts/doctor.py,
which reports secrets as set/unset, or --connector-url when the URL is actually needed.
Never ask the user for their Garmin password. Hand them the interactive login
(python scripts/setup_local.py) and let them type it into their own terminal.
The command is a script
Do not hand the user az or azd incantations to paste. Run the script; if a script
cannot do it, extend the script. Prose that drifts from reality is the specific failure
this repo already had.
| Task | Command |
|---|---|
| Set up locally | python scripts/setup_local.py |
| Diagnose anything | python scripts/doctor.py / --remote / --json |
| Deploy to Azure | python scripts/deploy.py |
| Register the Entra app | python scripts/entra_app.py |
| Upload the Garmin token | python scripts/seed_token.py |
| Rotate a secret | python scripts/rotate_secrets.py --help |
| Get the connector URL | python scripts/doctor.py --connector-url |
| Check before committing | python scripts/check_secrets.py |
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.
- 10d ago First seen · 137 lines · 1,673 tokens per session scan A aecb9f8f6051
garmin-coach-mcp CLAUDE.md is an instructions file published in the GitHub repository jhoy1020/garmin-coach-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,673 tokens to every session, about $0.0084 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).
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.
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).