setup-notifications-via-wecom

setup-notifications-via-wecom is a skill for Claude Code, Codex from daymade/claude-code-skills. It costs 90 tokens per session (2,384 once invoked), scanned B, original, MIT.

A workflow for sending technical status and alert messages through WeCom, Enterprise WeChat, using a group bot webhook.

In plain words
What is it for?
It helps configure and test a webhook and send status updates for backups, synchronisation jobs, scheduled tasks, or services.
Why use it?
It helps make automated notifications clear about what happened, what changed, and what each number means.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions Claude Code.

Good fit It helps configure and test a webhook and send status updates for backups, synchronisation jobs, scheduled tasks, or services.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/daymade/claude-code-skills/setup-notifications-via-wecom
About the project

Claude Code Skills Marketplace is a collection and marketplace of skills, plugins, agents, and instructions that extend Claude Code with specialized development workflows. It is for developers who want to install existing workflows or create, validate, and package their own Claude Code skills.

daymade/claude-code-skills · 1,384 stars · on GitHub

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 daymade/claude-code-skills --skill setup-notifications-via-wecom
Clone the repo
git clone --depth 1 https://github.com/daymade/claude-code-skills

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin setup-notifications-via-wecom/plugin install setup-notifications-via-wecom after adding the marketplace above.

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 setup-notifications-via-wecom

README.md
[![agentmods](https://agentmods.dev/badge/skills/daymade/claude-code-skills/setup-notifications-via-wecom/github.svg)](https://agentmods.dev/skills/daymade/claude-code-skills/setup-notifications-via-wecom)
Your own site
<a href="https://agentmods.dev/skills/daymade/claude-code-skills/setup-notifications-via-wecom"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/setup-notifications-via-wecom/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 setup-notifications-via-wecom

Your own site · 80×15
<a href="https://agentmods.dev/skills/daymade/claude-code-skills/setup-notifications-via-wecom"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/setup-notifications-via-wecom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,384 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 18
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Privilege Escalation · line 52
    Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
    Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
  • medium Data Exfiltration · line 212
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
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.00090 $0.02384
Opus 5 $0.00045 $0.01192
Sonnet 5 $0.00018 $0.00477
Haiku 4.5 $0.00009 $0.00238

Measured 5d ago against content hash a4503008ce55, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

setup-notifications-via-wecom scanned grade B with 2 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 5d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/send_wecom.py, scripts/set_recipient.py, tests/test_recipient_config.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

chmod 600 ~/.config/setup-notifications-via-wecom/config.json

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

### Option B: Inline curl
setup-notifications-via-wecom/SKILL.md · 277 lines

How it starts

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

Setup Notifications via WeCom

Overview

This skill helps you send clear, unambiguous technical notifications through a WeCom group bot webhook. It covers two things:

  1. One-time setup: store the webhook URL, test connectivity, and create a reusable sender script.
  2. Send messages: craft messages that distinguish state from delta, define every number, and avoid the misleading patterns that made earlier backup-sync notifications confusing.

The bundled script scripts/send_wecom.py handles the actual HTTP call, including the proxy-unset rule required for Tencent services in mainland China. Recipient identity is explicit configuration: self may send automatically; others requires human confirmation; missing identity fails fast.

When to Use This Skill

Trigger this skill when the user:

  • Says "send a WeCom notification", "企业微信通知", "企微机器人", or "webhook 通知".
  • Wants to set up alerting for a backup, sync, cron job, or service status.
  • Asks you to write a status/alert message and you need to make it clear and unambiguous.
  • Mentions a message was confusing or misleading and wants it fixed.

Quick Start: Configure the Webhook

  1. Check existing config:

    cat ~/.config/setup-notifications-via-wecom/config.json
    

    If it exists and contains webhook_url, skip to Send a Message.

  2. Get the webhook URL from the WeCom group bot settings. It looks like:

    https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY
    
  3. Store it privately (outside the skill bundle, so it survives updates):

    mkdir -p ~/.config/setup-notifications-via-wecom
    echo '{"webhook_url": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY"}' \
      > ~/.config/setup-notifications-via-wecom/config.json
    chmod 600 ~/.config/setup-notifications-via-wecom/config.json
    
  4. Classify the exact target and bind the canonical sender without exposing or rewriting the webhook value:

    uv run --no-project python scripts/set_recipient.py \
      --scope self --label "My private self channel"
    

    Use self only when the configured webhook is visible only to the user. Use others for every other person or group. Do not guess when the target is unknown. The command also records this sender's absolute path and digest; after the sender is upgraded, rerun the command before sending again.

Read the full file on GitHub · 277 lines

Files

What ships with it

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

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. 5d ago First seen · 277 lines · 90 tokens per session scan B a4503008ce55

Subscribe to this mod's changes

setup-notifications-via-wecom is a skill published in the GitHub repository daymade/claude-code-skills (1,384 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 2,384 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.