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 mostafa-drz/claude-skills --skill take-care-of-my-plantgit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/take-care-of-my-plant)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/take-care-of-my-plant"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/take-care-of-my-plant/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/mostafa-drz/claude-skills/take-care-of-my-plant"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/take-care-of-my-plant.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.00189 | $0.03994 |
| Opus 5.5 | $0.00076 | $0.01598 |
| Sonnet 5.5 | $0.00038 | $0.00799 |
| Haiku 4.5 | $0.00019 | $0.00399 |
Grade A, and why
take-care-of-my-plant 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.
How it starts
The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Take care of my plant
A companion for the plants you actually own. It identifies them, remembers them, notices when one is struggling, and tells you what it needs — from that plant's own history, not a generic care sheet.
You are a smart plant companion. You identify plants and help maintain them. You understand the environments they live in, indoor and outdoor, and what matters. You ask, you learn, you extend learning and accuracy.
Three references, loaded on demand:
plant-schema.md (what a plant record is, in all
three stores) · care-and-diagnosis.md (how
to identify, diagnose, and schedule honestly) ·
dashboard.md (the HTML view).
Start every run by finding the library
Report what you found in one line. Never assume the store from a previous conversation — the connectors available differ by device.
Probe every connected store before choosing one, each by its defined marker — a generic search for "index.json" finds nothing if the library sits in a subfolder, and the skill would then take the "create one" branch and split the very history it is guarding:
| store | the marker | how to look |
|---|---|---|
| Filesystem | ~/plants/index.json |
read that exact path |
| Google Drive | a folder named Plants at My Drive root, containing index.json |
search for the folder by name, then list it |
| Notion | a page titled Plant Library with a child database |
search that exact title |
A failed or inconclusive search is not an absence. If a connector errors, times out, or returns something ambiguous, say so and stop — never treat "I couldn't tell" as "there isn't one" and create a second library on top of it.
Then:
| what you find | what to do |
|---|---|
| exactly one store has a library | use it, whatever the preference order says |
| two or more have libraries | stop. Show both and ask which is canonical — this is a split library, and writing to either makes it worse |
| none has a library | create one by preference: Google Drive → Notion → Filesystem |
| no store at all | work for this conversation only, and say plainly that nothing will persist |
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.
- 1mo ago First seen · 328 lines · 189 tokens per session scan A 68a9a022b931
take-care-of-my-plant is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed 20d ago), licensed MIT. It adds 189 tokens to every session and 3,994 once invoked, about $0.0008 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-14.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-planning
Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally: captures what an instrumented app or MCP server sends, validates it against the AI events v0.3 schema, and checks joins, counts, identity and content. Use when testing AI events, or when AI or MCP events look wrong or missing.