zoho-mail-health-check

zoho-mail-health-check is a skill for Claude Code from MSApps-Mobile/claude-plugins. It costs 91 tokens per session (794 once invoked), scanned A, original, MIT.

A health-check procedure for two MSApps Zoho Mail accounts. It confirms the accounts exist, reads their five latest inbox messages, sends test emails, and saves a structured report.

In plain words
What is it for?
Use it when you need to verify that the two configured mail accounts are operational and record the results.
Why use it?
It helps identify whether account access, inbox reading, or outgoing mail is failing.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the zoho-mail-health plugin — 1 skill shipped together

Good fit Use it when you need to verify that the two configured mail accounts are operational and record the results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/msapps-mobile/claude-plugins/zoho-mail-health-check
Install

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.

Any agent
npx skills add MSApps-Mobile/claude-plugins --skill zoho-mail-health-check
Clone the repo
git clone --depth 1 https://github.com/MSApps-Mobile/claude-plugins

Made for: Claude Code.

Or install zoho-mail-health, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for zoho-mail-health-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/zoho-mail-health-check/github.svg)](https://agentmods.dev/skills/msapps-mobile/claude-plugins/zoho-mail-health-check)
Your own site
<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/zoho-mail-health-check"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/zoho-mail-health-check/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.

agentmods 80×15 button for zoho-mail-health-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/zoho-mail-health-check"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/zoho-mail-health-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 794 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.00794
Opus 5.5 $0.00036 $0.00318
Sonnet 5.5 $0.00018 $0.00159
Haiku 4.5 $0.00009 $0.00079

Measured 1mo ago against content hash c7355adc1b1e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zoho-mail-health-check 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.

plugins/zoho-mail-health/skills/zoho-mail-health-check/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Zoho Mail Health Check

Run a full health check on both MSApps Zoho Mail accounts and save a structured report.

Accounts to check

Account Inbox Folder ID
${ACCOUNT1_EMAIL} ${ACCOUNT1_INBOX_FOLDER_ID}
${ACCOUNT2_EMAIL} ${ACCOUNT2_INBOX_FOLDER_ID}

Step 1 — List accounts

Call zohomail_list_accounts. Confirm both ${ACCOUNT1_EMAIL} and ${ACCOUNT2_EMAIL} appear. If either is missing, mark it ❌ and skip remaining steps for that account.

Step 2 — Read 5 latest inbox messages (both accounts in parallel)

For each account call zohomail_list_messages with:

  • account_email: the account address
  • folder_id: the inbox folder ID from the table above
  • limit: 5

Record each message's subject and sender. If the call fails, mark that account's Read column ❌.

Step 3 — Send test emails (both accounts in parallel)

For each account call zohomail_send_message with:

  • account_email: the sending account
  • to: ${ACCOUNT1_EMAIL}
  • subject: [Health Check] YYYY-MM-DD HH:MM (current date/time in Israel time)
  • body: Automated health check from {account} at {datetime}. Zoho Mail MCP is operational.

If the call fails, mark that account's Send column ❌.

Step 4 — Save report

Save the report to the workspace Claude folder as zoho-health-check-YYYY-MM-DD.md.

Report structure:

# Zoho Mail Health Check — YYYY-MM-DD HH:MM IL

**Method used:** zohomail_* MCP tools
**Config fix required:** No / Yes (describe if yes)

## ✅/❌ Summary Table

| Account | Connect | Read | Send |
|---------|:---:|:---:|:---:|
| ${ACCOUNT1_EMAIL} | ✅/❌ | ✅/❌ | ✅/❌ |
| ${ACCOUNT2_EMAIL} | ✅/❌ | ✅/❌ | ✅/❌ |

## 📬 ${ACCOUNT1_EMAIL} — Last 5 Messages
1. **Subject** — from sender (date)
...

## 📬 ${ACCOUNT2_EMAIL} — Last 5 Messages
1. **Subject** — from sender (date)
...

## Notes
- Any issues, anomalies, or observations

Step 5 — Fallback (if zohomail_* MCP tools are unavailable)

If zohomail_list_accounts is not available in the session, fall back to the Python direct API method defined in the references/python-fallback.md file. Run the script via Bash and parse the output into the same report format. Note in the report that the fallback was used.

Read the full file on GitHub · 89 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 1mo ago First seen · 89 lines · 91 tokens per session scan A c7355adc1b1e

Subscribe to this mod's changes

zoho-mail-health-check is a skill published in the GitHub repository MSApps-Mobile/claude-plugins (9 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 794 once invoked, about $0.0004 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-13.

Related

Other skills, from other repositories

postmortem

Auto-generates a structured postmortem from a completed campaign. Reads the campaign file, telemetry logs, and feature ledger. Produces a documented analysis of what broke, what the safety systems caught, and what patterns emerged. Can also be invoked manually for any incident.

SethGammon/Citadel · 58 tokens

systematic-debugging

4-phase root cause analysis: observe, hypothesize, verify, fix. Enforces investigation before any code changes. Emergency stop after 2 failed fixes. Prevents shotgun debugging and fix cascades.

SethGammon/Citadel · 45 tokens

ai-diagnostic

A diagnostic framework that examines a problem across technology, processes, people, and business causes.

modu-ai/moai-cowork · 151 tokens

azure-mcp-observability

The read-only observability half of the azure-mcp connector — the monitor, resourcehealth, applens, and advisor namespaces: Azure Monitor metrics, Log Analytics KQL, alert-rule state, platform health states, AppLens detectors, and Advisor recommendation categories, plus the degraded-resource investigation order.

WYRE-AI/msp-claude-plugins · 66 tokens

diagnose-skill-run

Diagnose a failed or suspicious Runx skill execution from receipts and harness evidence, then propose the smallest bounded improvement without replaying the failed operation.

runxhq/runx · 35 tokens

postmortem-maker

Turn resolved-incident fragments into a traceable postmortem that separates fragment-cited facts from hypotheses, blocks publication while unknowns remain, and keeps the comms send behind a human gate.

runxhq/runx · 44 tokens