build-health-timeline

build-health-timeline is a skill for Codex from MarshallBear1/juno-open-health-tools. It costs 55 tokens per session (279 once invoked), scanned A, original, MIT.

A tool for arranging personal health observations, tests, appointments, medication changes, and changes in daily function into a dated timeline. It is for organising records, not diagnosing illness.

In plain words
What is it for?
Use it to record when symptoms or functional changes began, when treatments changed, and what improved or worsened. It keeps uncertain dates and reported diagnoses clearly marked.
Why use it?
It makes the sequence of health events easier to share with a clinician, include on a benefits form, or use during a care handoff without guessing missing facts.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit Use it to record when symptoms or functional changes began, when treatments changed, and what improved or worsened. It keeps uncertain dates and reported diagnoses clearly marked.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/marshallbear1/juno-open-health-tools/build-health-timeline
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 MarshallBear1/juno-open-health-tools --skill build-health-timeline
Clone the repo
git clone --depth 1 https://github.com/MarshallBear1/juno-open-health-tools

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 build-health-timeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/marshallbear1/juno-open-health-tools/build-health-timeline/github.svg)](https://agentmods.dev/skills/marshallbear1/juno-open-health-tools/build-health-timeline)
Your own site
<a href="https://agentmods.dev/skills/marshallbear1/juno-open-health-tools/build-health-timeline"><img src="https://agentmods.dev/badge/skills/marshallbear1/juno-open-health-tools/build-health-timeline/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 build-health-timeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/marshallbear1/juno-open-health-tools/build-health-timeline"><img src="https://agentmods.dev/badge/skills/marshallbear1/juno-open-health-tools/build-health-timeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 279 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.00055 $0.00279
Opus 5.5 $0.00022 $0.00112
Sonnet 5.5 $0.00011 $0.00056
Haiku 4.5 $0.00006 $0.00028

Measured 2mo ago against content hash 05cabfd7e043, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

build-health-timeline 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 2mo 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.

plugins/juno-health-tools/skills/build-health-timeline/SKILL.md · 19 lines

What it actually says

Build a health timeline

Privacy gate

Before sending text to the Juno Health Tools MCP server, disclose that it will be processed transiently without intentional application storage and ask whether the user wants to continue. Invoke the tool only after explicit agreement and set consentConfirmed to true. Ask only for brief, user-authored, non-identifying observations. Do not request or accept PHI, names, contact details, record or insurance numbers, credentials, provider documents, or text copied from a clinical system.

  1. Keep dates exactly as supplied; use “date uncertain” when needed.
  2. Separate observations, reported diagnoses, tests, treatments, and user-suspected triggers.
  3. Sort chronologically and merge only true duplicates.
  4. Highlight first onset, material worsening or improvement, medication changes, and changes in function.
  5. Produce a short “what changed overall” summary that states facts and uncertainty.

Never convert correlation into causation. Attribute clinical statements, for example “user reports clinician diagnosed …”. Do not fill missing dates or results from memory.

Files

What ships with it

1 file 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. 2mo ago First seen · 19 lines · 55 tokens per session scan A 05cabfd7e043

Subscribe to this mod's changes

build-health-timeline is a skill published in the GitHub repository MarshallBear1/juno-open-health-tools (1 stars, last pushed 4d ago), licensed MIT. It adds 55 tokens to every session and 279 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

opik-diagnose

Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…

comet-ml/opik-mcp · 187 tokens

ue-mcp-epic-routing

Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.

db-lyon/ue-mcp · 81 tokens

qa-knowledge

To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.

griddynamics/rosetta · 32 tokens

apitap

ApiTap gives AI agents cheap access to web data through three layers.

n1byn1kt/apitap · 0 tokens

frontmcp-setup

Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…

agentfront/frontmcp · 176 tokens

x-use-review

Daily digest for an x-use account covering health, metrics, pending drafts, and queued work in one pass, then approve/reject/process per the user's direction. Use for "how is my account doing", daily check-ins, or before any batch of approvals.

ihuzaifashoukat/x-use · 56 tokens