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.
npx skills add philipyaz/cos --skill fitness-health-datagit clone --depth 1 https://github.com/philipyaz/cosWrote 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/skills/philipyaz/cos/fitness-health-data)<a href="https://agentmods.dev/skills/philipyaz/cos/fitness-health-data"><img src="https://agentmods.dev/badge/skills/philipyaz/cos/fitness-health-data/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/skills/philipyaz/cos/fitness-health-data"><img src="https://agentmods.dev/badge/skills/philipyaz/cos/fitness-health-data.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.00259 | $0.04638 |
| Opus 5 | $0.00130 | $0.02319 |
| Sonnet 5 | $0.00052 | $0.00928 |
| Haiku 4.5 | $0.00026 | $0.00464 |
Grade A, and why
fitness-health-data scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**`fitness`** MCP — never `bash`/`curl` (Cowork's sandbox blocks outbound HTTP; the tools How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fitness — health data (the data-plane operator)
This skill is the intelligence that turns a plain-language health note — "push last
night's sleep", "I ran 5k this morning", "what's my HRV doing", "how was my day",
"delete that bad entry" — into structured health records on the board, and that archives a
health report into the vault. The health data plumbing runs only through the
fitness MCP — never bash/curl (Cowork's sandbox blocks outbound HTTP; the tools
exist for exactly this). The board UI is the read twin: the human glances at
/fitness/health (the Apple Watch dashboard); the agent (you) does the ingestion, the reads,
the fixes, and the vault archive.
The data this skill ingests is the fuel for everything else: the coaching skills (training
plan, weekly review, pre-workout brief, correlations) and the /fitness/health dashboard all
read the entries you push here. Get the data in clean and they work; push a malformed entry and
they silently see nothing.
Scope — this is the DATA half. This skill does ingest + query + maintain + vault. It does NOT design training plans (fitness-training-plan), weekly reviews (fitness-weekly-review), pre-workout briefs (fitness-pre-workout-brief), or correlations (fitness-correlations), and it does NOT create or edit the athlete profile (that's the fitness-athlete-profile skill). If the user asks for a plan, a review, a brief, correlations, to set their training focus/sports (fitness-athlete-profile), or to set their body goal / training status / weight (body-profile), hand off to the right sibling skill.
Gate — the add-on must be ENABLED. Every WRITE (
push_health_data,delete_health_data) 404s ("Not found — the fitness add-on may be disabled.") when the Fitness add-on is disabled; READS always work. If a write comes back "Not found.", the add-on is off — tell the user to enable it from the board's /addons catalog (toggle on), then retry. You don't enable it yourself; it's a deliberate, human, one-time switch.
Attribution. The MCP stamps health writes as the agent (the
x-actor: agentheader), and the board's activity log records them. There is no pending / propose queue for health — these tools write directly. So "approval" here means a conversational check-in (STEP 0), not the board's propose/approve flow. Don't claim a pending queue exists.
NOT MEDICAL ADVICE — say it whenever you interpret. You only log what the user (or their export) provides — but the moment you read back and interpret a number (a low HRV, poor sleep, an elevated resting HR), frame it as an informational estimate, not medical advice. Defer to a professional (a physician or qualified clinician) for any abnormal symptom, chest pain, injury, illness, pregnancy, or a user under 18 — recommend they consult one. Never diagnose from biometric data.
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 · 263 lines · 259 tokens per session scan A 0393db171342
fitness-health-data is a skill published in the GitHub repository philipyaz/cos (4 stars, last pushed yesterday), licensed MIT. It adds 259 tokens to every session and 4,638 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
wiki-lint
Health-check a wiki vault. Finds orphan pages (no inbound links), dead wikilinks (point to non-existent pages), missing frontmatter fields, stale claims, empty sections, and pages absent from catalog.md. Produces a structured report with severity tiers and proposes concrete fixes — but does not auto-apply them unless…
opencode-plugin-idioms
Event hook payload shapes, session lifecycle timing, toast/TUI-route render boundaries, and child-session tagging conventions for OpenCode server (@opencode-ai/plugin) and TUI (@opencode-ai/plugin/tui) plugins, grounded in the vendored OpenCode source at references/opencode.
meta-sync-template
Interactive flow to propagate the reference (.template) vault's plugins, snippets, and root docs to one or more configured vaults. Reads the active router config, lists every vault with online status, flags vaults missing obsidian-local-rest-api upfront, lets the user pick all or a subset, and optionally re-clones…
save
File the current Claude conversation (or a specific insight from it) as a structured wiki note. Auto-detects the right type (decision, answer, session-log, technique, ADR), writes appropriate frontmatter, places the file in the correct wiki folder, and updates catalog.md, journal.md, hot.md. Use when the user says…
wiki-export
Export a vault's wiki either as a single portable file (llms.txt or llms-full.txt per the llmstxt.org standard) or as an OKF knowledge bundle (Google's Open Knowledge Format v0.1 — a shareable directory of markdown files any AI agent can consume). Use when the user says "export my wiki", "make an llms.txt", "share my…
wiki-boundary
Rank the "frontier" pages of a wiki — the crossroads many pages link to that stay thin inside — so you can decide where research would pay off most. Use when the user says "what should I write about next", "where are the gaps", "which pages need work", "find the thin hub pages", "boundary pages", "/wiki-boundary"…