Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/agentlas-ai/agentlas-desktopnpx agentmods add skills/agentlas-ai/agentlas-desktop/treatment-plansWrote 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/agentlas-ai/agentlas-desktop/treatment-plans)<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/treatment-plans"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/treatment-plans/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/agentlas-ai/agentlas-desktop/treatment-plans"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/treatment-plans.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.00062 | $0.02183 |
| Opus 5.5 | $0.00025 | $0.00873 |
| Sonnet 5.5 | $0.00012 | $0.00437 |
| Haiku 4.5 | $0.00006 | $0.00218 |
Grade A, and why
treatment-plans 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 1mo 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.
This is a copy
100% identical to treatment-plans — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Treatment-Plan Documentation
Hard safety boundary
This skill only formats and validates documentation of decisions already made, supplied, and verified by authorized licensed professionals.
Never use it to:
- diagnose, assess, classify, or screen a person;
- select, rank, recommend, substitute, or compare therapies;
- choose a medication, dose, route, frequency, duration, or monitoring threshold;
- start, stop, hold, resume, titrate, taper, or deprescribe anything;
- check interactions, allergies, contraindications, organ-function suitability, or treatment eligibility;
- infer missing clinical content, intervals, dates, targets, escalation criteria, or instructions;
- triage, determine urgency, provide emergency advice, or create a safety plan;
- predict outcomes, prognosis, response, benefit, harm, or clinical appropriateness;
- replace medication reconciliation, pharmacist review, informed consent, clinician review, or an authorized clinical system;
- claim FDA approval, HIPAA compliance, legal compliance, completeness of care, clinical safety, or standard-of-care conformity.
If a request crosses a boundary, stop. Ask for a locally verified clinician-authored record or route the matter to the responsible licensed professional. Do not redirect to another skill to obtain a patient-specific recommendation.
If a concern may be urgent or emergent, stop this workflow and route it through the institution's current clinical escalation or emergency process. This skill does not decide urgency and does not provide emergency instructions.
Required visible notice
Every component and derived schedule must display:
DRAFT — NOT MEDICAL ADVICE — DOCUMENTATION-ONLY — AUTHORIZED CLINICIAN SIGN-OFF REQUIRED
Structural success never removes this notice. Only the authorized local workflow may set the release gate.
Data gate
Prefer synthetic or qualified de-identified structured manifests. Do not place patient names, medical-record numbers, contact details, dates of birth, addresses, free-text notes, images, or other direct identifiers in examples.
What ships with it
22 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.
- assets/clinician_authored_intervention_template.json 408 B
- assets/goals_monitoring_checkpoint_template.json 446 B
- assets/informed_preference_shared_decision_template.json 408 B
- assets/intended_use_handoff_template.json 2.9 KB
- assets/source_fact_manifest_template.json 381 B
- assets/transition_reconciliation_template.json 880 B
- references/documentation_workflow.md 6.4 KB
- references/privacy_governance.md 5.6 KB
- references/README.md 1.4 KB
- references/safety_scope.md 5.2 KB
- references/security_validation.md 3.6 KB
- references/shared_decision_handoff.md 5.3 KB
- references/source_boundaries.md 6.1 KB
- references/source_ledger.md 7.6 KB
- scripts/_common.py 39 KB runs code
- scripts/check_completeness.py 18 KB runs code
- scripts/check_consistency.py 12 KB runs code
- scripts/generate_template.py 3.7 KB runs code
- scripts/privacy_process_check.py 6.4 KB runs code
- scripts/timeline_generator.py 7.9 KB runs code
- scripts/validate_traceability.py 4.5 KB runs code
- scripts/validate_treatment_plan.py 2.5 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.
- 1mo ago First seen · 192 lines · 62 tokens per session scan A 9d806eb6556b
treatment-plans is a skill published in the GitHub repository agentlas-ai/agentlas-desktop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 62 tokens to every session and 2,183 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to treatment-plans, differing in 25 lines, and is treated as a copy.
Other skills, from other repositories
cua-volume
Use Cua Volume, the one volume every Space and agent of this user shares. Inside a Space it is mounted as a folder (/volume on Linux, /Cua Volume on macOS), so any program reads and writes it directly. Use it for anything that must outlive this Space - your memory and outputs in your agent home, shared reference in…
doc-ingest
Extract readable text from document files — PDF, XLSX/CSV/TSV, DOCX, PPTX, and plain-text formats — so any task that arrives with an attachment can actually consume it.
md2pdf
Convert a Markdown file to PDF with GitHub-style formatting using the md2pdf tool.
delive-transcript-analyzer
Analyze, summarize, and extract insights from DeLive transcription sessions. Use when: user mentions DeLive, transcription, meeting transcripts, live captions, audio transcription, AI correction, corrected transcript, or transcript analysis; user wants to search, retrieve, summarize, correct, or process recorded…
hermesoffice-documents
Produce and edit Word documents in HermesOffice Docs — block editing, tracked changes, reports, and the templates/docs library (meeting notes, business plan, PRD, decision memo, and more). Load for any request that creates or restructures a document.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.