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.
/plugin marketplace add zhanyoulin456/seevin-claude-pluginsnpx agentmods add plugins/zhanyoulin456/seevin-claude-plugins/seevin-yapi-toolsgit clone --depth 1 https://github.com/zhanyoulin456/seevin-claude-pluginsWrote 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/zhanyoulin456/seevin-claude-plugins/seevin-yapi-tools)<a href="https://agentmods.dev/plugins/zhanyoulin456/seevin-claude-plugins/seevin-yapi-tools"><img src="https://agentmods.dev/badge/plugins/zhanyoulin456/seevin-claude-plugins/seevin-yapi-tools.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
seevin-yapi-tools 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 3d 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": "seevin-yapi-tools",
"description": "YAPI 接口文档自动化工具 - 根据接口文档生成 JS/TS 代码，需配置个人 YAPI 凭证",
"version": "1.0.0",
"author": {
"name": "Seevin Team",
"email": "[email protected]"
},
"license": "MIT",
"mcpServers": "./.mcp.json",
"commands": "./commands",
"homepage": "https://github.com/zhanyoulin456/seevin-claude-plugins/tree/main/plugins/seevin-yapi-tools#readme"
}
What it installs
The manifest is a name and a version. 2 commands travel with it, and installing the plugin installs all of them — 18 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.
- 3d ago First seen · 14 lines scan A 015ccbba6f17
seevin-yapi-tools is a plugin published in the GitHub repository zhanyoulin456/seevin-claude-plugins (4 stars, last pushed 7mo 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-31.
Other plugins, from other repositories
kernel-sdks
TypeScript and Python SDK skills for building browser automation with Kernel's Typescript and Python SDKs.
typescript-expert
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between…
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins marketplace
Plugin marketplace listing 98 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.