analyze

analyze is a skill for Claude Code from Itsokay-co/bio-vibing. It costs 52 tokens per session (3,065 once invoked), scanned A, original, Apache-2.0.

An event-impact analysis that compares biometric data before and after something changed in your life. It can also compare several dates when the change happened in stages, such as increasing a dose.

In plain words
What is it for?
Use it to study events such as stopping alcohol, starting creatine, or beginning a new job, using one or more event dates.
Why use it?
It gives you a structured way to examine whether an event coincided with changes in your health data. The comparison can include glucose variation, oxygen levels, sleep, and cycle phase.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the bio-vibing plugin — 8 skills shipped together

Good fit Use it to study events such as stopping alcohol, starting creatine, or beginning a new job, using one or more event dates.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Itsokay-co/bio-vibing
Claude Code
/plugin install bio-vibing

Made for: Claude Code.

Or install bio-vibing, the plugin that ships this one along with the rest of its 8 skills.

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 analyze

README.md
[![agentmods](https://agentmods.dev/badge/skills/itsokay-co/bio-vibing/analyze.svg)](https://agentmods.dev/skills/itsokay-co/bio-vibing/analyze)
Your own site
<a href="https://agentmods.dev/skills/itsokay-co/bio-vibing/analyze"><img src="https://agentmods.dev/badge/skills/itsokay-co/bio-vibing/analyze.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,065 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.00052 $0.03065
Opus 5 $0.00026 $0.01533
Sonnet 5 $0.00010 $0.00613
Haiku 4.5 $0.00005 $0.00307

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

Security

Grade A, and why

analyze 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 8d 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/analyze/SKILL.md · 229 lines

How it starts

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

Analyze — Event Impact & Dose Tracking

Compare biometric data before and after a life event. Supports multiple event dates for dose escalation tracking.

Arguments

  • First argument: event name (e.g., "Quit alcohol", "Started creatine", "New job")
  • Second argument: event date(s) — single date (YYYY-MM-DD) or comma-separated for dose changes (e.g., "2026-02-02,2026-03-02,2026-03-30")

Steps

EVENT_NAME="${1:-Event}"
EVENT_DATES="${2:-$(date +%Y-%m-%d)}"
python3 << PYEOF
import sys, os
sys.path.insert(0, os.path.join(os.environ.get('CLAUDE_PLUGIN_ROOT', '.'), 'lib'))
from fetch import fetch_biometrics
from cycle import detect_cycle_phases
from dataclasses import asdict
from datetime import datetime, timedelta
from statistics import mean, stdev
from collections import defaultdict
from metrics import compute_disruption_classification, compute_glucose_variability

event_name = "$EVENT_NAME"
event_dates_str = "$EVENT_DATES"
event_dates = [d.strip() for d in event_dates_str.split(",")]

first_event = datetime.strptime(event_dates[0], "%Y-%m-%d")
pre_start = (first_event - timedelta(days=28)).strftime("%Y-%m-%d")
post_end = datetime.now().strftime("%Y-%m-%d")

print(f"Analyzing: {event_name}")
print(f"Event date(s): {', '.join(event_dates)}")
print(f"Pre-period: {pre_start} to {event_dates[0]}")
print(f"Post-period: {event_dates[0]} to {post_end}")

data = fetch_biometrics(start_date=pre_start, end_date=post_end)
d = asdict(data)

sleep = [s for s in d['sleep'] if s.get('sleep_type') in ('long_sleep', None)] or d['sleep']

def safe_mean(vals): return mean(vals) if vals else 0
def safe_stdev(vals): return stdev(vals) if len(vals) > 1 else 0

# --- PRE/POST COMPARISON ---
def split_pre_post(records, event_date, date_key="day"):
    pre = [r for r in records if r.get(date_key, "") < event_date]
    post = [r for r in records if r.get(date_key, "") >= event_date]
    return pre, post

def compare(pre_vals, post_vals, label, unit="", higher_is_better=True):
    if not pre_vals or not post_vals: return None
    pre_mean = safe_mean(pre_vals)
    post_mean = safe_mean(post_vals)
    if pre_mean == 0: return None
    pct = ((post_mean - pre_mean) / abs(pre_mean)) * 100
    pre_sd = safe_stdev(pre_vals)
    significant = abs(post_mean - pre_mean) > pre_sd if pre_sd > 0 else abs(pct) > 10
    direction = "up" if pct > 0 else "down"
    good = (direction == "up" and higher_is_better) or (direction == "down" and not higher_is_better)
    return {"label": label, "pre": f"{pre_mean:.1f}{unit}", "post": f"{post_mean:.1f}{unit}",
            "change": f"{pct:+.1f}%", "significant": significant,
            "flag": "GOOD" if good and significant else ("FLAG" if not good and significant else ""),
            "pre_mean": pre_mean, "post_mean": post_mean}

# Main comparison against first event date
pre_sleep, post_sleep = split_pre_post(sleep, event_dates[0])
pre_ready, post_ready = split_pre_post(d['readiness'], event_dates[0])

results = []
if sleep:
    results.append(compare([s['score'] for s in pre_sleep if s.get('score')], [s['score'] for s in post_sleep if s.get('score')], "Sleep Score", "", True))
    for field, label, unit, hib in [
        ("deep_sleep_seconds", "Deep Sleep", " min", True),
        ("rem_sleep_seconds", "REM Sleep", " min", True),
        ("total_sleep_seconds", "Total Sleep", " min", True),
        ("efficiency", "Efficiency", "%", True),
        ("avg_hrv_ms", "HRV", " ms", True),
        ("avg_resting_hr_bpm", "Resting HR", " bpm", False),
    ]:
        div = 60 if "seconds" in field else 1
        results.append(compare([s[field]/div for s in pre_sleep if s.get(field)], [s[field]/div for s in post_sleep if s.get(field)], label, unit, hib))

if d['readiness']:
    results.append(compare([r['score'] for r in pre_ready if r.get('score')], [r['score'] for r in post_ready if r.get('score')], "Readiness", "", True))
    results.append(compare([r['temp_deviation_c'] for r in pre_ready if r.get('temp_deviation_c') is not None], [r['temp_deviation_c'] for r in post_ready if r.get('temp_deviation_c') is not None], "Temp Deviation", "°C", False))

results = [r for r in results if r is not None]

print(f"\n{'='*70}")
print(f"BEFORE / AFTER: {event_name}")
print(f"{'='*70}\n")
print(f"{'Metric':<20} {'Pre':>10} {'Post':>10} {'Change':>10} {'Signal':>8}")
print("-" * 62)
for r in results:
    sig = " ***" if r["significant"] else ""
    flag = f"  {r['flag']}" if r["flag"] else ""
    print(f"{r['label']:<20} {r['pre']:>10} {r['post']:>10} {r['change']:>10}{flag}{sig}")

significant = [r for r in results if r["significant"]]
if significant:
    print(f"\nKEY FINDINGS:")
    for f in significant:
        tag = f["flag"] or "NOTE"
        print(f"  [{tag}] {f['label']}: {f['pre']} → {f['post']} ({f['change']})")

# --- DOSE ESCALATION TRACKING ---
if len(event_dates) > 1:
    print(f"\n{'='*70}")
    print(f"DOSE ESCALATION TIMELINE")
    print(f"{'='*70}")
    for i, date in enumerate(event_dates):
        label = f"Dose {i+1}" if i > 0 else "Start"
        next_date = event_dates[i+1] if i+1 < len(event_dates) else post_end
        period_sleep = [s for s in sleep if date <= s.get('day', '') < next_date]

        hrv_vals = [s['avg_hrv_ms'] for s in period_sleep if s.get('avg_hrv_ms')]
        rhr_vals = [s['avg_resting_hr_bpm'] for s in period_sleep if s.get('avg_resting_hr_bpm')]
        eff_vals = [s['efficiency'] for s in period_sleep if s.get('efficiency')]

        days_in_period = (datetime.strptime(next_date, "%Y-%m-%d") - datetime.strptime(date, "%Y-%m-%d")).days
        print(f"\n  {label} ({date}, {days_in_period} days):")
        if hrv_vals: print(f"    HRV: {safe_mean(hrv_vals):.0f}ms")
        if rhr_vals: print(f"    RHR: {safe_mean(rhr_vals):.1f}bpm")
        if eff_vals: print(f"    Efficiency: {safe_mean(eff_vals):.0f}%")

# --- CYCLE PHASE CONTEXT ---
tags = d.get('tags', [])
cycle = detect_cycle_phases(d['readiness'], sleep, period_tags=tags or None)
if cycle['current_phase'] != 'unknown':
    print(f"\n  Cycle detection ({cycle['source']}, confidence: {cycle['confidence']}):")
    print(f"    Current phase: {cycle['current_phase']} (day {cycle['estimated_cycle_day']})")
    print(f"    Cycle length: ~{cycle['cycle_length']} days")
    if cycle['detected_periods']:
        print(f"    Detected periods: {', '.join(cycle['detected_periods'])}")
    # Check if any event dates fall in luteal phase
    for ed in event_dates:
        for period_start in cycle['detected_periods']:
            gap = (datetime.strptime(ed, "%Y-%m-%d") - datetime.strptime(period_start, "%Y-%m-%d")).days
            if 14 <= gap <= cycle.get('cycle_length', 28):
                print(f"    Note: {ed} falls in estimated luteal phase — biometric shifts may overlap")

# --- HR ZONES COMPARISON ---
heartrate = d.get('heartrate', [])
if heartrate:
    from metrics import compute_hr_zones, compute_intensity_minutes
    user = d.get('user') or {}
    pre_hr = [h for h in heartrate if h.get('timestamp', '')[:10] < event_dates[0]]
    post_hr = [h for h in heartrate if h.get('timestamp', '')[:10] >= event_dates[0]]
    if pre_hr and post_hr:
        pre_im = compute_intensity_minutes(pre_hr, user)
        post_im = compute_intensity_minutes(post_hr, user)
        if pre_im['combined_minutes'] or post_im['combined_minutes']:
            print(f"\n  Intensity minutes (combined):")
            print(f"    Pre:  {pre_im['combined_minutes']} min")
            print(f"    Post: {post_im['combined_minutes']} min")

# --- Personal Baseline Context (NEW) ---
from metrics import compute_personal_baselines
bl = compute_personal_baselines(sleep, readiness)
if bl.get('status') == 'ok':
    print(f"\n  BASELINE CONTEXT:")
    for mk in ['hrv', 'rhr', 'sleep_score', 'efficiency']:
        m = bl['metrics'].get(mk, {})
        b30 = m.get('baselines', {}).get('30d', {})
        if b30.get('mean') is not None:
            # Where does post-period sit vs full baseline?
            post_vals = [s.get({'hrv': 'avg_hrv_ms', 'rhr': 'avg_resting_hr_bpm',
                               'sleep_score': 'score', 'efficiency': 'efficiency'}[mk])
                        for s in post_sleep
                        if s.get({'hrv': 'avg_hrv_ms', 'rhr': 'avg_resting_hr_bpm',
                                 'sleep_score': 'score', 'efficiency': 'efficiency'}[mk]) is not None]
            if post_vals:
                post_mean = mean(post_vals)
                z = round((post_mean - b30['mean']) / max(b30['sd'], 0.001), 2)
                print(f"    {mk}: post-period {round(post_mean, 1)} vs 30d baseline {b30['mean']} (z={'+' if z>0 else ''}{z})")

# --- Gut Score Context (NEW, if Suna connected) ---
gut_scores = d.get('gut_scores', [])
if gut_scores:
    pre_gs = [g['score'] for g in gut_scores if g.get('day', '') < event_dates[0] and g.get('score')]
    post_gs = [g['score'] for g in gut_scores if g.get('day', '') >= event_dates[0] and g.get('score')]
    if pre_gs and post_gs:
        print(f"\n  GUT SCORE:")
        print(f"    Pre:  {round(mean(pre_gs))} avg (n={len(pre_gs)})")
        print(f"    Post: {round(mean(post_gs))} avg (n={len(post_gs)})")
        diff = round(mean(post_gs) - mean(pre_gs))
        print(f"    Change: {'+' if diff>0 else ''}{diff}")

# Disruption events in the analysis window
disrupt = compute_disruption_classification(d.get('sleep', []), d.get('readiness', []), d.get('spo2', []))
events_in_window = [e for e in disrupt.get('events', []) if e.get('day', '') >= event_dates[0]]
if events_in_window:
    print(f"\nDISRUPTION EVENTS (post-event):")
    for e in events_in_window:
        print(f"  {e['day']}: {e['classification'].replace('probable_', '')} ({e['recovery_shape']}-shape)")

# Glucose context if CGM connected
glucose = d.get('glucose', [])
if glucose:
    gv = compute_glucose_variability(glucose)
    if gv.get('mean'):
        print(f"\nGLUCOSE:")
        print(f"  Mean: {gv['mean']} mg/dL | CV: {gv['cv']}% | TIR: {gv['time_in_range_pct']}%")

print()
PYEOF

Read the full file on GitHub · 229 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. 8d ago First seen · 229 lines · 52 tokens per session scan A e5e532739c97

Subscribe to this mod's changes

analyze is a skill published in the GitHub repository Itsokay-co/bio-vibing (16 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 3,065 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens