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.
git 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/plugins/daymade/claude-code-skills/setup-notifications-via-wecom)<a href="https://agentmods.dev/plugins/daymade/claude-code-skills/setup-notifications-via-wecom"><img src="https://agentmods.dev/badge/plugins/daymade/claude-code-skills/setup-notifications-via-wecom.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
setup-notifications-via-wecom 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 4d 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.
What it actually says
{
"name": "setup-notifications-via-wecom",
"description": "Set up and send technical status notifications through WeCom (Enterprise WeChat) webhooks. Use this skill whenever the user needs to send notifications, alerts, backup completion reports, or status updates via WeCom; when they mention 企业微信, 企微机器人, webhook, or alerting; or when a message needs to be clear, unambiguous, and technically precise rather than vague or condescending.",
"source": "./setup-notifications-via-wecom",
"strict": false,
"version": "1.0.0",
"category": "developer-tools",
"keywords": [
"wecom",
"enterprise-wechat",
"notifications",
"webhook",
"alerts",
"企业微信",
"企微机器人",
"status-updates",
"claude-code"
]
}What ships with it
1 file beside marketplace.json#setup-notifications-via-wecom 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.
- 4d ago First seen · 19 lines scan A 0d45c9aad135
setup-notifications-via-wecom is a plugin published in the GitHub repository daymade/claude-code-skills (1,381 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.
Other plugins, from other repositories
dev-workflows-fullstack
Skills + Subagents for fullstack development (backend + React/TypeScript) - Use skills for coding guidance, or run recipe workflows for full orchestrated agentic coding with specialized agents.
sessy
Track AWS SES bounces, complaints, and delivery stats from Claude Code. Requires a Sessy API key. Does not send email or change SES settings.
api
Extract API endpoints from GitHub repos, online docs, or local files and import them as sdkck CLI commands.
shipmail
Operate secure custom-domain business email, calendars, and agent inboxes with Shipmail.
render-useful-mcp
Manage Render services, deploys, databases and logs. Wraps all 208 endpoints of the Render Public API plus workflow tools for finding services by name, waiting on deploys and triaging failures.
mailbox
Multi-mailbox IMAP/SMTP control plane exposed as a REST API and MCP server on a single port — read, search, send, mark-seen, and delete mail across multiple inboxes.