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 magic3007/dotfiles --skill treatment-plansgit clone --depth 1 https://github.com/magic3007/dotfilesWrote 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/magic3007/dotfiles/treatment-plans)<a href="https://agentmods.dev/skills/magic3007/dotfiles/treatment-plans"><img src="https://agentmods.dev/badge/skills/magic3007/dotfiles/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/magic3007/dotfiles/treatment-plans"><img src="https://agentmods.dev/badge/skills/magic3007/dotfiles/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.00086 | $0.11597 |
| Opus 5 | $0.00043 | $0.05798 |
| Sonnet 5 | $0.00017 | $0.02319 |
| Haiku 4.5 | $0.00009 | $0.01160 |
Grade B, and why
treatment-plans scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo cp assets/medical_treatment_plan.sty /usr/local/texlive/texmf-local/tex/latex/ This is a copy
100% identical to treatment-plans — 13 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 — 1,582 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Treatment Plan Writing
Overview
Treatment plan writing is the systematic documentation of clinical care strategies designed to address patient health conditions through evidence-based interventions, measurable goals, and structured follow-up. This skill provides comprehensive LaTeX templates and validation tools for creating concise, focused treatment plans (3-4 pages standard) across all medical specialties with full regulatory compliance.
Critical Principles:
- CONCISE & ACTIONABLE: Treatment plans default to 3-4 pages maximum, focusing only on clinically essential information that impacts care decisions
- Patient-Centered: Plans must be evidence-based, measurable, and compliant with healthcare regulations (HIPAA, documentation standards)
- Minimal Citations: Use brief in-text citations only when needed to support clinical recommendations; avoid extensive bibliographies
Every treatment plan should include clear goals, specific interventions, defined timelines, monitoring parameters, and expected outcomes that align with patient preferences and current clinical guidelines - all presented as efficiently as possible.
When to Use This Skill
This skill should be used when:
- Creating individualized treatment plans for patient care
- Documenting therapeutic interventions for chronic disease management
- Developing rehabilitation programs (physical therapy, occupational therapy, cardiac rehab)
- Writing mental health and psychiatric treatment plans
- Planning perioperative and surgical care pathways
- Establishing pain management protocols
- Setting patient-centered goals using SMART criteria
- Coordinating multidisciplinary care across specialties
- Ensuring regulatory compliance in treatment documentation
- Generating professional treatment plans for medical records
Visual Enhancement with Scientific Schematics
⚠️ MANDATORY: Every treatment plan MUST include at least 1 AI-generated figure using the scientific-schematics skill.
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/chronic_disease_management_plan.tex 29 KB
- assets/general_medical_treatment_plan.tex 23 KB
- assets/medical_treatment_plan.sty 5.3 KB
- assets/mental_health_treatment_plan.tex 34 KB
- assets/one_page_treatment_plan.tex 5.3 KB
- assets/pain_management_plan.tex 33 KB
- assets/perioperative_care_plan.tex 29 KB
- assets/quality_checklist.md 15 KB
- assets/rehabilitation_treatment_plan.tex 30 KB
- assets/STYLING_QUICK_REFERENCE.md 3.8 KB
- references/goal_setting_frameworks.md 16 KB
- references/intervention_guidelines.md 19 KB
- references/README.md 17 KB
- references/regulatory_compliance.md 17 KB
- references/specialty_specific_guidelines.md 26 KB
- references/treatment_plan_standards.md 16 KB
- scripts/check_completeness.py 9.7 KB runs code
- scripts/generate_schematic_ai.py 32 KB runs code
- scripts/generate_schematic.py 5.0 KB runs code
- scripts/generate_template.py 7.3 KB runs code
- scripts/timeline_generator.py 12 KB runs code
- scripts/validate_treatment_plan.py 12 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 · 1,582 lines · 86 tokens per session scan B 05c0ef142635
treatment-plans is a skill published in the GitHub repository magic3007/dotfiles (11 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 11,597 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 100% identical to treatment-plans, differing in 13 lines, and is treated as a copy.
Other skills, from other repositories
overleaf
Read and write Overleaf projects from the CLI using an existing web session — list and create projects, list/read/write/delete files, mirror a local directory into a project, compile it and pull the PDF. Works on a free account, where Overleaf's git and GitHub bridges are premium-only. Use when the user references an…
md2pdf
Convert a Markdown file to PDF with GitHub-style formatting using the md2pdf tool.
remarkable
Render a Markdown or Org document to a PDF for reading on Petar's reMarkable Paper Pure, in the clean classic CS/Lisp-paper aesthetic (Computer Modern Book, small-caps numbered sections, monochrome code, links as footnotes), using pandoc and tectonic. Use when the user asks for a PDF for the reMarkable, a "paper PDF"…
orchestrate-agents
Orchestrate multiple agent CLIs (Claude, Codex, Antigravity) via tmux with a shared fleet store, dispatching one guardian subagent per pane. Survey-first: inspects and adopts existing tmux sessions, windows, and agent panes before creating anything new. Use when running a multi-agent session, dispatching parallel…
assess-quality
Foundational quality framework: the five questions (readable, easy to start, expands without bloat, consistent, intentional) every other dev skill is judged against, plus the dual-audience and workshop principles. Use when onboarding to a project, defining a quality bar, setting an assessment checklist, or arbitrating…
create-oss-skill
Create well-formed Agent Skills following the agentskills.io specification. Scaffold directories, write SKILL.md files, bundle scripts, and structure instructions for progressive disclosure. Use when creating a new skill, reviewing skill structure, optimizing a skill description, or setting up evals for skill quality.