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.
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 daymade/claude-code-skills --skill notify-wecomgit clone --depth 1 https://github.com/daymade/claude-code-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/daymade/claude-code-skills/notify-wecom)<a href="https://agentmods.dev/skills/daymade/claude-code-skills/notify-wecom"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/notify-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.
<a href="https://agentmods.dev/skills/daymade/claude-code-skills/notify-wecom"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/notify-wecom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 42 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.
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.00073 | $0.00746 |
| Opus 5 | $0.00036 | $0.00373 |
| Sonnet 5 | $0.00015 | $0.00149 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
notify-wecom scanned grade A with 1 finding 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.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. Sends via the WeCom webhook using the sender from `setup-notifications-via-wecom` (or an equivalent inline curl call). How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/notify-wecom
Send a single message to a WeCom group bot.
Human confirmation boundary
Read the explicit recipient_scope and recipient_label from the shared config.
self is the user's own delivery channel and may send without authorization.
others requires the active human-confirmation gate with the exact label and
message. Missing/invalid scope is a configuration error: stop and classify the
target; do not guess. A local alert/outbox item still needs identity/content
validation before either route.
Usage
/notify-wecom Claude Code 备份完成 ✅
The skill reads the webhook URL from the shared config file:
~/.config/setup-notifications-via-wecom/config.json
If the config is missing, it prints the one-line setup command and stops.
Prerequisite
This skill is a lightweight companion to setup-notifications-via-wecom. Either:
- Install
setup-notifications-via-wecomfirst (recommended — it provides the webhook setup steps and its bundled sender), or - Create the config file manually as shown below.
What It Does
- Reads
~/.config/setup-notifications-via-wecom/config.jsonforwebhook_url,recipient_scope, andrecipient_label. - Unsets all local proxy env vars (Tencent endpoints must be reached directly).
- If scope is
self, sends without an authorization prompt. If scope isothers, presents the exact label and message for human confirmation. - Sends via the WeCom webhook using the sender from
setup-notifications-via-wecom(or an equivalent inline curl call). - Reports success or the exact WeCom error; authorization alone is not delivery proof.
Examples
/notify-wecom 服务上线成功 🚀
/notify-wecom 告警：build 失败，请检查
/notify-wecom 今日同步完成，0 缺失 0 滞后
Multi-line Messages
For multi-line messages, wrap in triple quotes or use a file:
/notify-wecom "第一行
第二行
第三行"
Failure Modes
- Config missing: Run the setup step from
setup-notifications-via-wecom, or create the config file manually. - Recipient or sender identity missing/invalid: Use
setup-notifications-via-wecom'sset_recipient.pycommand; never infer self versus others from the webhook URL, and never trust a script merely because its basename issend_wecom.py. - Webhook key invalid: WeCom returns an
errcode; the skill prints it. - Proxy still interfering: If you have proxy vars set outside the standard names, unset them first.
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.
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.
- 5d ago First seen · 83 lines · 73 tokens per session scan A beacf9424364
notify-wecom is a skill published in the GitHub repository daymade/claude-code-skills (1,384 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 746 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…