heavenly-health-protocol: Instructions file for Codex

AGENTS.md

heavenly-health-protocol AGENTS.md is an instructions file for Codex, OpenCode from xbirimensah/heavenly-health-protocol. It costs 678 tokens per session, scanned A, original, MIT.

Repository instructions for Heavenly Health Protocol, a project that connects AI clients to health data controlled by its users. They define privacy, compatibility, communication, and runtime rules for contributors and coding agents.

In plain words
What is it for?
Guiding code changes, tests, error messages, examples, releases, and configuration so they follow the project's privacy and compatibility requirements.
Why use it?
They reduce the risk of exposing health records, credentials, private repository history, or deployment-specific details during development.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is xbirimensah/heavenly-health-protocol's own configuration. It tells Codex and OpenCode how to work on heavenly-health-protocol 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 heavenly-health-protocol configures →

Reuse

Borrowing it

Nothing to install: this file belongs to xbirimensah/heavenly-health-protocol. 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/xbirimensah/heavenly-health-protocol/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/xbirimensah/heavenly-health-protocol

Made for: Codex, OpenCode.

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 heavenly-health-protocol AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/xbirimensah/heavenly-health-protocol/agents-md/github.svg)](https://agentmods.dev/instructions/xbirimensah/heavenly-health-protocol/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/xbirimensah/heavenly-health-protocol/agents-md"><img src="https://agentmods.dev/badge/instructions/xbirimensah/heavenly-health-protocol/agents-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.

agentmods 80×15 button for heavenly-health-protocol AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/xbirimensah/heavenly-health-protocol/agents-md"><img src="https://agentmods.dev/badge/instructions/xbirimensah/heavenly-health-protocol/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 678 This file is loaded in full into every session.
When invoked 678 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.00678 $0.00678
Opus 5 $0.00339 $0.00339
Sonnet 5 $0.00136 $0.00136
Haiku 4.5 $0.00068 $0.00068

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

Security

Grade A, and why

heavenly-health-protocol 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 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.

AGENTS.md · 74 lines

How it starts

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

AGENTS.md

Project scope

Heavenly Health Protocol is an LLM-agnostic MCP boundary over user-controlled health data. Preserve compatibility with generic MCP clients; never make one model, agent vendor, provider account, deployment domain, or operator identity a runtime requirement.

Non-negotiable privacy rules

  • Never commit .env, runtime.env, handover files, logs, database dumps, access/refresh tokens, OAuth callback codes, assertions, API keys, private keys, provider payloads, health records, or local agent state.
  • Keep owner names, emails, domains, Cloudflare team/account/application IDs, Supabase project references, table overrides, and absolute workstation paths in runtime variables outside Git.
  • Examples use reserved domains such as example.com, generic identities such as [email protected], and placeholder identifiers.
  • Never print credential values in tests, exceptions, previews, diffs, or MCP tool results. Error messages may name a missing variable, not its value.
  • Do not make an existing private repository or its history public. Public releases use a validated tracked-file export and a fresh Git history.

Product communication

  • Lead ordinary users through the native path: configured data → native MCP → client connection.
  • Cloudflare Managed OAuth uses Dynamic Client Registration. Compatible MCP clients normally leave optional client ID and client secret fields blank.
  • Keep Docker, tunnel reconciliation, origin JWT validation, and the CLI-agent sandbox in advanced operator documentation.
  • Clearly distinguish implemented adapters from provider specifications. Google Health API v4 is implemented and live-verified for native use. Garmin, WHOOP, and Oura are implemented (native OAuth, bounded sync, refresh, revocation, and record normalization), but their live-data paths depend on account access and are not yet verified against real records: Garmin needs an approved Garmin evaluation account, WHOOP an active membership, and Oura recent data within the granted scopes. Health Connect remains a specification until corresponding code and live verification exist.

Read the full file on GitHub · 74 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. 10d ago First seen · 74 lines · 678 tokens per session scan A e99071e1f3b3

Subscribe to this mod's changes

heavenly-health-protocol AGENTS.md is an instructions file published in the GitHub repository xbirimensah/heavenly-health-protocol (0 stars, last pushed 2d ago), licensed MIT. It adds 678 tokens to every session, about $0.0034 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-09-01.

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

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

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

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