connect

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

A connection check for wearable health services such as Oura Ring, Whoop, Fitbit, and Apple Health. It identifies the configured service and reports whether data can be accessed.

In plain words
What is it for?
Use it to test a wearable connection and see what health data is available.
Why use it?
It helps find setup or access problems before you try to analyze your health data. It also shows which data source is available when more than one is configured.

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 test a wearable connection and see what health data is available.

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 connect

README.md
[![agentmods](https://agentmods.dev/badge/skills/itsokay-co/bio-vibing/connect.svg)](https://agentmods.dev/skills/itsokay-co/bio-vibing/connect)
Your own site
<a href="https://agentmods.dev/skills/itsokay-co/bio-vibing/connect"><img src="https://agentmods.dev/badge/skills/itsokay-co/bio-vibing/connect.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 681 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.00042 $0.00681
Opus 5 $0.00021 $0.00341
Sonnet 5 $0.00008 $0.00136
Haiku 4.5 $0.00004 $0.00068

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

Security

Grade A, and why

connect 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/connect/SKILL.md · 96 lines

How it starts

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

Connect

Test the wearable API connection and report what data is available.

Steps

  1. Detect which wearable is configured and test the connection:
python3 << 'PYEOF'
import sys, os
sys.path.insert(0, os.path.join(os.environ.get('CLAUDE_PLUGIN_ROOT', '.'), 'lib'))
from providers import detect_provider, get_provider, list_configured_providers, PROVIDERS

# Show detection result
configured = list_configured_providers()
if not configured:
    env_vars = [f"  {v['env']} ({k})" for k, v in PROVIDERS.items()]
    print("ERROR: No wearable configured.")
    print("Set one of these environment variables:")
    print("\n".join(env_vars))
    sys.exit(1)

active = detect_provider()
print(f"Detected provider: {active}")
if len(configured) > 1:
    print(f"All configured: {', '.join(configured)}")
    print(f"(Override with BIOMETRIC_PROVIDER env var)")

# Test connection
provider = get_provider(active)
result = provider.test_connection()

if not result["connected"]:
    print(f"\nERROR: Connection failed — {result['info']}")
    sys.exit(1)

print(f"\nConnected to {active}")
print(f"  {result['info']}")

# Check available data
from datetime import datetime, timedelta
end = datetime.now().strftime("%Y-%m-%d")
start = (datetime.now() - timedelta(days=365)).strftime("%Y-%m-%d")

print(f"\nAvailable data:")
counts = provider.fetch_available_data(start, end)
for endpoint, count in counts.items():
    print(f"  {endpoint.replace('_', ' ').title()}: {count} records")

# Fetch user profile
profile = provider.fetch_user_profile()
if profile:
    parts = []
    if profile.age: parts.append(f"{profile.age}y")
    if profile.biological_sex: parts.append(profile.biological_sex)
    if profile.weight_kg: parts.append(f"{profile.weight_kg}kg")
    if profile.height_m: parts.append(f"{profile.height_m}m")
    if parts:
        print(f"\nUser: {', '.join(parts)}")

print(f"\nReady to biohack.")
PYEOF

Output Format

Present the results as:

Detected provider: [provider]

Connected to [provider]
  [user info]

Available data:
  Sleep:     [N] records
  Readiness: [N] records
  Activity:  [N] records
  Stress:    [N] records

User: [age]y, [sex], [weight]kg

Ready to biohack.

Read the full file on GitHub · 96 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 · 96 lines · 42 tokens per session scan A c3389a72c01d

Subscribe to this mod's changes

connect is a skill published in the GitHub repository Itsokay-co/bio-vibing (16 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 681 once invoked, about $0.0002 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

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

jetson-diagnostic

Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.

NVIDIA/skills · 30 tokens

doca-socket-relay

Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…

NVIDIA/skills · 236 tokens

offensive-z-wave

Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…

SnailSploit/Claude-Red · 113 tokens

hsb-flash

Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…

NVIDIA/skills · 94 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens