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 mpaarating/ai-workflow-kit --skill plantsgit clone --depth 1 https://github.com/mpaarating/ai-workflow-kitWrote 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/mpaarating/ai-workflow-kit/plants)<a href="https://agentmods.dev/skills/mpaarating/ai-workflow-kit/plants"><img src="https://agentmods.dev/badge/skills/mpaarating/ai-workflow-kit/plants/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/mpaarating/ai-workflow-kit/plants"><img src="https://agentmods.dev/badge/skills/mpaarating/ai-workflow-kit/plants.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.00013 | $0.00709 |
| Opus 5.5 | $0.00005 | $0.00284 |
| Sonnet 5.5 | $0.00003 | $0.00142 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
plants 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 2mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plants
Keep your houseplants alive. Track watering, status, and care needs in one place.
Trigger Phrases
- "water plants"
- "plant update"
- "plant check"
- "how are my plants"
- "new plant: [name]"
Workflow
On "plant check" / "how are my plants"
Read the plant database and display a status table:
| Plant | Status | Last Watered | Water Needs | Light |
|----------------|------------|--------------|-------------|---------|
| Pothos | Thriving | Mar 17 | Weekly | Low |
| Fiddle Leaf | Struggling | Mar 10 | Biweekly | Bright |
| Snake Plant | Healthy | Mar 15 | Monthly | Any |
Flag any plants that are overdue for watering based on their schedule and last watered date.
On "water plants" / "watered [plant]"
Update the "Last Watered" date for the specified plant(s) to today.
- If no specific plant named, ask: "Which plants did you water? Or all of them?"
- If "all", update every plant
- Confirm:
Logged: Watered Pothos, Snake Plant (Mar 19)
On "new plant: [name]"
Add a new plant to the database. Ask for (or infer from the plant name):
- Water needs: Weekly, Biweekly, Monthly
- Light needs: Low, Medium, Bright, Any
- Pet-friendly: Yes/No
Set initial status to "New" and last watered to today.
If the user provides just a name, look up common care requirements for that plant species and suggest defaults. Confirm before saving.
Added: "Monstera" — Bright light, weekly water, not pet-friendly. Status: New
On "plant update" / status change
Update a plant's status. Valid statuses:
- Thriving — Growing well, new leaves
- Healthy — Normal, no concerns
- Struggling — Yellowing, drooping, pests
- New — Recently acquired
Ask what changed if not specified. Update the record and confirm.
Storage
Using {{notes}}: Store as a database/table with columns: Name, Status, Water Needs, Light Needs, Last Watered, Next Repot, Pet-Friendly.
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.
- 2mo ago First seen · 103 lines · 13 tokens per session scan A cd476e19b1ab
plants is a skill published in the GitHub repository mpaarating/ai-workflow-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 709 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…