google-health-readonly

google-health-readonly is a skill for Codex from paceaitian/google-health-chatgpt-selfhost. It costs 67 tokens per session (1,058 once invoked), scanned A, original, Apache-2.0.

A read-only connection for reviewing one user’s Google Health records, such as activity, sleep, vital signs, body measurements, exercise, trends, and irregular-rhythm notifications.

In plain words
What is it for?
Use it to retrieve daily totals, time-based rollups, individual records, sleep or exercise sessions, latest measurements, or irregular-rhythm history.
Why use it?
It provides a bounded way to query health records without writing data, diagnosing conditions, or inventing measurements when results are missing.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to retrieve daily totals, time-based rollups, individual records, sleep or exercise sessions, latest measurements, or irregular-rhythm history.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/paceaitian/google-health-chatgpt-selfhost/google-health-readonly
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add paceaitian/google-health-chatgpt-selfhost --skill google-health-readonly
Clone the repo
git clone --depth 1 https://github.com/paceaitian/google-health-chatgpt-selfhost

Made for: Codex.

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 google-health-readonly

README.md
[![agentmods](https://agentmods.dev/badge/skills/paceaitian/google-health-chatgpt-selfhost/google-health-readonly/github.svg)](https://agentmods.dev/skills/paceaitian/google-health-chatgpt-selfhost/google-health-readonly)
Your own site
<a href="https://agentmods.dev/skills/paceaitian/google-health-chatgpt-selfhost/google-health-readonly"><img src="https://agentmods.dev/badge/skills/paceaitian/google-health-chatgpt-selfhost/google-health-readonly/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.

agentmods 80×15 button for google-health-readonly

Your own site · 80×15
<a href="https://agentmods.dev/skills/paceaitian/google-health-chatgpt-selfhost/google-health-readonly"><img src="https://agentmods.dev/badge/skills/paceaitian/google-health-chatgpt-selfhost/google-health-readonly.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,058 The whole file, excluding the scripts and references it only reads on demand.
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.00067 $0.01058
Opus 5 $0.00034 $0.00529
Sonnet 5 $0.00013 $0.00212
Haiku 4.5 $0.00007 $0.00106

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

Security

Grade A, and why

google-health-readonly 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.

skills/google-health-readonly/SKILL.md · 38 lines

How it starts

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

Google Health read-only workflow

Call the connector before stating facts about the connected user's Google Health data. Never replace a failed or empty tool result with an inferred measurement.

Translate the request into its metric, result granularity, closed-open range, query time zone, and data-source family. Select the operation with this routing table:

Requested result Tool Request method
Calendar-day totals or day-by-day trends google_health_daily_rollup Select one rollup dataType and a closed-open civil-date range.
5-minute, 15-minute, 1-hour, 6-hour, or 24-hour buckets google_health_physical_rollup Select one rollup dataType, an explicit-offset RFC 3339 range, and the matching windowSize.
Daily, sample, interval, sleep-session, exercise-session, or latest records google_health_reconcile Select one reconcile dataType and civil startDate/endDateExclusive; the connector generates the reviewed filter.
Irregular-rhythm notification history google_health_irn_list Supply civil startDate/endDateExclusive and a page size up to 10.

Use references/query-catalog.md for the exact type-to-method matrix, range limits, source families, and pagination details. Common mappings include:

  • steps, distance, activity minutes, activity energy, heart-rate aggregates, and other day totals → the matching daily rollup type;
  • resting heart rate → daily-resting-heart-rate;
  • daily HRV → daily-heart-rate-variability; HRV samples → heart-rate-variability;
  • daily blood oxygen → daily-oxygen-saturation; blood-oxygen samples → oxygen-saturation;
  • sleep temperature → daily-sleep-temperature-derivations; sleep sessions → sleep;
  • daily respiratory rate → daily-respiratory-rate; sleep respiratory summary → respiratory-rate-sleep-summary;
  • daily, running, and sample VO2 max → daily-vo2-max, run-vo2-max, and vo2-max respectively.

Keep every range closed-open and as narrow as the request permits. Resolve relative dates in the user's intended time zone. Respect the tool's 14-day limits for heart-rate, active-minutes, calories-in-heart-rate-zone, and total-calories rollups; the 90-day general limit; pageSize<=25 for sleep/exercise reconcile; other page-size limits; and fixed partial-response masks. Daily rollup must fit completely in one page because the current Google response has no nextPageToken. Physical rollup, reconcile, and IRN may follow a returned token only with every other input unchanged and only when the request needs another page. Any returned nextPageToken means the query is incomplete even when that page has no records; do not classify the query as empty until the required page walk reaches a response without a token.

Disambiguate completeness. “Cover every supported category” means the 34 non-IRN data types plus IRN, using the catalog's preferred projection for each type. “Return every raw record” additionally requires following every token-bearing reconcile or IRN query to completion and can be large; physical rollup is still used only when the user explicitly requests sub-day buckets. For ordinary analysis, select the daily, session, interval, or sample types that directly answer the question and use the requested granularity.

For scheduled summaries, save a self-contained prompt that names the MCP connection, the exact tool/data types, the intended query time zone and closed-open range, and the page limit. Set and verify the scheduler's own time zone separately; a time zone written only inside the data-query prompt does not control when the task runs. This repository's local Skill is documentation and evaluation material: a Developer Mode MCP connection receives the server instructions, tool descriptions, and schemas, but does not automatically import this Skill into web ChatGPT. Verify the real app association and keep the necessary query contract in the Scheduled prompt itself. Treat connector unavailable, OAuth invalid, permission denied, rate limited, upstream failure, and an actual empty result as different outcomes.

Read the full file on GitHub · 38 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 12d ago First seen · 38 lines · 67 tokens per session scan A 187b363500f4

Subscribe to this mod's changes

google-health-readonly is a skill published in the GitHub repository paceaitian/google-health-chatgpt-selfhost (1 stars, last pushed 18d ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,058 once invoked, about $0.0003 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.