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 realactivity/tula --skill myhealth-pulsegit clone --depth 1 https://github.com/realactivity/tulaWrote 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/realactivity/tula/myhealth-pulse)<a href="https://agentmods.dev/skills/realactivity/tula/myhealth-pulse"><img src="https://agentmods.dev/badge/skills/realactivity/tula/myhealth-pulse/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/realactivity/tula/myhealth-pulse"><img src="https://agentmods.dev/badge/skills/realactivity/tula/myhealth-pulse.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.00100 | $0.01176 |
| Opus 5 | $0.00050 | $0.00588 |
| Sonnet 5 | $0.00020 | $0.00235 |
| Haiku 4.5 | $0.00010 | $0.00118 |
Grade A, and why
myhealth-pulse 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
myhealth-pulse
When to Use
✅ Use when:
- User says "run myhealth-pulse", "check my health feeds", "daily pulse"
- Scheduled invocation - daily, weekly, or per-feed cadence from the profile
- User asks for mentions, alerts, or a topic digest across configured feeds
- A new feed adapter was enabled and the user wants a unified view
When NOT to Use
❌ Don't use when:
- User shares a PDF, screenshot, or image -> use
med-pdf - User asks about their chart, labs, meds -> use
health-records - User wants to draft a clinician message -> use
epic-note - User asks for medical advice - decline politely; this is aggregation, not clinical judgment
- Anything that would put PHI into an outbound query string
Setup
Profile. Resolve from the precedence in
references/profile-schema.md
(skill config -> env var -> ~/.openclaw/workspace/memory/profile.yaml).
The skill never contains the profile. If none resolves, return one line
saying so and stop. Don't fabricate.
Feed adapters. Each profile.feeds.enabled entry maps to an adapter
in references/feeds.md. The
agent must have the adapter's underlying tool available. Missing tool ->
skip that feed with a one-line note in the output.
Workflow
-
Load and validate the profile. Resolve the path, parse YAML, validate against the schema. Refuse on missing or malformed profile.
-
Resolve enabled adapters. For each
profile.feeds.enabledentry, look up the contract inreferences/feeds.md. Drop adapters whose tool isn't available; remember which were dropped. -
Build and call. Substitute profile fields into each adapter's query template. Apply the active window (
dailyfor ad-hoc,weeklyfor "weekly pulse") via the adapter's native time filter. Call all adapters in parallel. -
Score and filter. Apply the shared rubric in
references/feeds.md. Keep items at or aboveprofile.feeds.thresholds.keep_score. Cap atmax_items. Dedupe by URL and near-identical title.
What ships with it
4 files 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.
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.
- 11d ago First seen · 114 lines · 100 tokens per session scan A 457370273e05
myhealth-pulse is a skill published in the GitHub repository realactivity/tula (45 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 100 tokens to every session and 1,176 once invoked, about $0.0005 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.
Other skills, from other repositories
healthcare-expert
Expert-level healthcare systems, medical informatics, HIPAA compliance, and health data standards. Use when the user mentions medical, HIPAA, HL7, FHIR, or EHR, or when the task involves Healthcare IT, Standards and Protocols, Regulatory Compliance, or Security and Compliance.
ehr-data-parsing
Parse and extract clinical data from HL7v2 messages and FHIR R4 resources using Python. Use when the user mentions HL7v2, HL7, FHIR, PID segment, OBX segment, MSH segment, Patient resource, Observation resource, Condition resource, MedicationRequest, EHR data extraction, clinical message parsing, FHIR bundle, HL7 to…
telemetry-inspect
Inspects the OrchestKit telemetry pipeline for the current project — lists all known telemetry files with write counts, sizes, schema status, growth trend, and orphan detection. Use when verifying the observability pipeline is healthy, debugging a missing writer, or auditing which files have schema locks vs. which are…
biomcp-research
Do biomedical literature and variant research with the BioMCP CLI, and file what you learn about the tool itself as issues in the biomcp repo.
system_status
Check system health -- disk usage, memory, running processes, uptime.
branch_health
Quick health check -- test counts and file stats for AIPass branches.