Borrowing it
Nothing to install: this file belongs to diegoscarabelli/garmin-health-data. 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/diegoscarabelli/garmin-health-data/main/CLAUDE.mdgit clone --depth 1 https://github.com/diegoscarabelli/garmin-health-dataWrote 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/diegoscarabelli/garmin-health-data/claude-md)<a href="https://agentmods.dev/instructions/diegoscarabelli/garmin-health-data/claude-md"><img src="https://agentmods.dev/badge/instructions/diegoscarabelli/garmin-health-data/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/diegoscarabelli/garmin-health-data/claude-md"><img src="https://agentmods.dev/badge/instructions/diegoscarabelli/garmin-health-data/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.01240 | $0.01240 |
| Opus 5 | $0.00620 | $0.00620 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
garmin-health-data 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 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.
How it starts
The opening of the file, as written. The whole thing — 158 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.
README.md
The most important source of truth is the /README.md file, which contains the latest information about the project. You MUST read and understand the README.md file in order to provide accurate and relevant responses and coding assistance.
The README.md file includes:
- Introduction: Project overview, objectives, and features for extracting Garmin Connect health data to a local SQLite database.
- Features: Comprehensive data extraction, automatic deduplication, FIT file processing, and flexible authentication.
- Installation: Installation instructions via pip or from source.
- Quick Start: Authentication setup and basic usage examples.
- Usage: Detailed commands for data extraction, initialization, and status checking.
- Data Categories: Complete list of available data types with extraction frequency.
- Database Schema: Schema documentation with inline comments, SQLite adaptations, and table structure.
- Repository Structure: Overview of code organization (
garmin_health_data/,tests/). - Development: Setup instructions for contributors.
- Comparisons: Feature comparison with other tools (garmindb, garmy, etc.).
Database Schema Architecture
Following the openetl pattern, the database schema is defined in garmin_health_data/tables.ddl:
- tables.ddl: Single source of truth for database schema with inline SQL comments.
- models.py: SQLAlchemy ORM models for data processing ONLY (not schema generation).
- db.py: Executes tables.ddl to create schema automatically.
Schema Documentation
Inline comments in tables.ddl are preserved in the SQLite database and can be viewed:
sqlite3 garmin_data.db "SELECT sql FROM sqlite_master WHERE type='table' AND name='activity';"
Formatting DDL Files
Use SQLFluff to format the DDL file (configured in pyproject.toml):
python -m sqlfluff fix garmin_health_data/tables.ddl
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 · 158 lines · 1,240 tokens per session scan A dd1948b59311
garmin-health-data CLAUDE.md is an instructions file published in the GitHub repository diegoscarabelli/garmin-health-data (116 stars, last pushed today), licensed Apache-2.0. It adds 1,240 tokens to every session, about $0.0062 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.
Other instructions, from other repositories
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.
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).
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).