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 agentmods add skills/realactivity/tula/prep-my-visitnpx skills add realactivity/tula --skill prep-my-visitgit 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/prep-my-visit)<a href="https://agentmods.dev/skills/realactivity/tula/prep-my-visit"><img src="https://agentmods.dev/badge/skills/realactivity/tula/prep-my-visit.svg" alt="Measured on agentmods" 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 | $0.00055 | $0.00457 |
| Opus 5 | $0.00028 | $0.00229 |
| Sonnet 5 | $0.00011 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
prep-my-visit 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 5d 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.
What it actually says
prep-my-visit
Prepare an IPS-aligned pre-visit package.
When to Use
Use when:
- Upcoming visit prep request from patient or caregiver
- Pre-visit lab question for an upcoming appointment
- Request for handoff summary, goals list, or portal snippet drafts
When NOT to Use
Don't use when:
- Any diagnosis, treatment, or medication-change request
- Billing/insurance/prior-auth/EOB request
- Standalone PDF extraction request -> use
med-pdf - Standalone portal drafting request -> use
epic-note - Any PHI transfer outside
~/.openclaw/workspace/
Workflow
- Resolve visit context and choose template.
- Capture 1-3 patient goals verbatim.
- Run lab analysis using
references/lab-analyzer.md. - Build IPS + Tula extensions using
references/ips-contract.md. - Draft provider/patient views and snippets using
references/workflow.md. - Validate outputs with
references/scripts.md. - Persist outputs in
~/.openclaw/workspace/tula/briefs/{visit_id}/.
Scripts
Run the commands documented in references/scripts.md.
Examples
Privacy
- Keep PHI in
~/.openclaw/workspace/. - Never auto-send snippets; patient approval is required.
- Reject insurance/billing/prior-auth/EOB content.
Troubleshooting
- Missing data: return constrained draft + missing-items list.
- Category B overflow or imperative phrasing: keep top three and rewrite to discuss-with-doctor wording.
What ships with it
17 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.
- README.md 4.2 KB
- references/examples.md 2.1 KB
- references/examples/cardiology-followup.json 8.7 KB
- references/examples/cardiology-followup.labs.json 997 B
- references/examples/pcp-annual.json 6.1 KB
- references/examples/pcp-annual.labs.json 1.5 KB
- references/examples/urgent-same-day.json 3.7 KB
- references/examples/urgent-same-day.labs.json 154 B
- references/ips-contract.md 1.0 KB
- references/lab-analyzer.md 1.6 KB
- references/scripts.md 854 B
- references/workflow.md 1.4 KB
- scripts/.gitignore 19 B
- scripts/enforce_snippet_limits.mjs 1.3 KB runs code
- scripts/render_visit_brief.py 33 KB runs code
- scripts/validate_ips_sections.mjs 1.7 KB runs code
- scripts/validate_lab_opportunities.mjs 1.9 KB runs code
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.
- 5d ago First seen · 63 lines · 55 tokens per session scan A de3a4418eea8
prep-my-visit is a skill published in the GitHub repository realactivity/tula (45 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 457 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.
Other skills, from other repositories
comment-compactor
Delete the comments a diff adds unless they earn their place, and condense the few that do. Use as the final step before pushing, submitting, or finalizing a PR — after tests and lint pass, before git push / gh pr create. Also use when asked to "clean up the comments", "check the comments", or when a review flags a…
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.