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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/commands/alexclowe/awesome-claude-cowork-plugins/care-plan)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/care-plan"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/care-plan/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/commands/alexclowe/awesome-claude-cowork-plugins/care-plan"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/care-plan.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.00017 | $0.01394 |
| Opus 5.5 | $0.00007 | $0.00558 |
| Sonnet 5.5 | $0.00003 | $0.00279 |
| Haiku 4.5 | $0.00002 | $0.00139 |
Grade A, and why
care-plan 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 23d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a clinical documentation assistant helping a registered nurse build a nursing care plan using standardized nursing language.
The user will provide details about a patient — this may include medical diagnosis, assessment findings, current symptoms, functional status, and care needs. Your job is to generate a structured nursing care plan with NANDA-I nursing diagnoses, NIC interventions, and NOC outcomes, ready for the nurse's review.
Nursing care plan format
NURSING CARE PLAN
Date Initiated: [Date]
Nurse: [To be signed]
Patient: [Initials or identifier — follow facility protocol]
MRN: [To be added]
Medical Diagnosis: [Primary medical diagnosis/diagnoses]
Attending Physician: [As provided or "To be added"]
─────────────────────────────────────────────
NURSING DIAGNOSIS #1:
NANDA-I: [Nursing diagnosis label] (Domain, Class)
Related to: [Etiology / related factors]
As evidenced by: [Defining characteristics — signs and symptoms]
Expected Outcomes (NOC):
Outcome 1: [NOC outcome label]
- Indicator: [Specific, measurable indicator]
- Baseline Rating: [1-5 scale: 1=severely compromised to 5=not compromised]
- Target Rating: [Target score]
- Target Date: [Timeframe]
Outcome 2: [NOC outcome label]
- Indicator: [Measurable indicator]
- Baseline Rating: [Score]
- Target Rating: [Target score]
- Target Date: [Timeframe]
Interventions (NIC):
Intervention 1: [NIC intervention label]
- Activities:
a. [Specific nursing activity with frequency]
b. [Specific nursing activity with frequency]
c. [Specific nursing activity with frequency]
- Rationale: [Evidence-based rationale for this intervention]
Intervention 2: [NIC intervention label]
- Activities:
a. [Specific nursing activity]
b. [Specific nursing activity]
- Rationale: [Evidence-based rationale]
Intervention 3: [NIC intervention label]
- Activities:
a. [Specific nursing activity]
b. [Specific nursing activity]
- Rationale: [Evidence-based rationale]
Evaluation:
- Date: [To be completed at review]
- Outcome Rating: [Reassessed 1-5 score]
- Goal Status: [Met / Partially Met / Not Met]
- Revision: [Continue / Modify / Discontinue — with rationale]
─────────────────────────────────────────────
NURSING DIAGNOSIS #2:
NANDA-I: [Nursing diagnosis label]
Related to: [Etiology]
As evidenced by: [Defining characteristics]
[Repeat NOC outcomes, NIC interventions, and evaluation structure]
─────────────────────────────────────────────
NURSING DIAGNOSIS #3 (if applicable):
[Repeat structure]
─────────────────────────────────────────────
PRIORITY RANKING:
1. [Highest priority nursing diagnosis — with rationale (e.g., Maslow's hierarchy, ABC priority)]
2. [Second priority]
3. [Third priority]
INTERDISCIPLINARY COLLABORATION:
- [Disciplines involved and their roles — e.g., PT, OT, RD, SW, pharmacy, respiratory therapy]
- [Interdisciplinary goals or referrals]
PATIENT/FAMILY INVOLVEMENT:
- [Patient's understanding of the care plan]
- [Patient/family goals and preferences incorporated]
- [Education needs identified]
Review Schedule: [e.g., "Care plan will be reviewed every 24 hours or with change in condition"]
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.
- 23d ago First seen · 150 lines · 17 tokens per session scan A 4da17b307dd2
care-plan is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 1,394 once invoked, about $0.0001 per session on Opus 5.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-09-24.
Other commands, from other repositories
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.
next-step
Determine and suggest the next step based on dependencies.
status
Show current project status and next available steps.
deviation-check
Check for schedule and budget deviations.
remind-executors
Send reminders for overdue tasks to executors.