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 askads/claude-pluginsnpx agentmods add plugins/askads/claude-plugins/yandex-direct-apigit clone --depth 1 https://github.com/askads/claude-pluginsGrade A, and why
yandex-direct-api 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 yesterday.
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": "yandex-direct-api",
"displayName": "Yandex Direct API (own token)",
"version": "1.0.0",
"description": "Full Yandex Direct API v5 with your own OAuth token via the mcp-yandex-direct npm server: statistics, keywords, bids, budgets — including write tools behind explicit confirmation. Requires Node.js 20+.",
"author": {
"name": "Ask Ads",
"email": "[email protected]",
"url": "https://askads.ru"
},
"homepage": "https://github.com/askads/mcp-yandex-direct",
"repository": "https://github.com/askads/claude-plugins",
"license": "MIT",
"keywords": [
"yandex-direct",
"yandex",
"ppc",
"advertising",
"api"
],
"userConfig": {
"token": {
"type": "string",
"title": "Yandex Direct OAuth token",
"description": "OAuth token with Yandex Direct API access — see github.com/askads/mcp-yandex-direct for how to get one",
"sensitive": true,
"required": true
},
"client_login": {
"type": "string",
"title": "Client login (agencies only)",
"description": "Managed client login for agency tokens; leave empty for a regular advertiser account",
"default": ""
}
}
}
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.
- yesterday First seen · 37 lines scan A 351de57434c6
yandex-direct-api is a plugin published in the GitHub repository askads/claude-plugins (2 stars, last pushed 21d 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
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.