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/Oaklight/weilinkWrote 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/oaklight/weilink/claude_code)<a href="https://agentmods.dev/plugins/oaklight/weilink/claude_code"><img src="https://agentmods.dev/badge/plugins/oaklight/weilink/claude_code/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/plugins/oaklight/weilink/claude_code"><img src="https://agentmods.dev/badge/plugins/oaklight/weilink/claude_code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
weilink 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.
What it actually says
{
"name": "weilink",
"description": "WeChat messaging for Claude Code — receive and send WeChat messages, download media, and manage bot sessions via the iLink Bot protocol.",
"version": "0.6.0",
"author": {
"name": "Oaklight",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 1 skill, 1 hook, 1 MCP server travel with it, and installing the plugin installs all of them — 46 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 10 lines scan A 161074c274b0
weilink is a plugin published in the GitHub repository Oaklight/weilink (17 stars, last pushed 1mo ago), 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-08-30.
Other plugins, from other repositories
agents-for-js
Skills for building agents with the Microsoft 365 Agents SDK for TypeScript/JavaScript.
agents-for-dotnet
Skills for building agents with the Microsoft 365 Agents SDK for DotNet.
agents-for-python
Skills for building agents with the Microsoft 365 Agents SDK for Python.
agents-sdk-common
Shared skills for building agents with the Microsoft 365 Agents SDK (all languages).
python-toolkit
Python development toolkit with UV for fast package management, project structure, and dependency management. Includes python expert agent for strategic Python architecture decisions.
mailrith
Manage Mailrith email marketing through focused, permission-scoped tools.