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/ztemerbekov/a1-yandex-kit-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/mcp/ztemerbekov/a1-yandex-kit-skills/a1-yandex-kit)<a href="https://agentmods.dev/mcp/ztemerbekov/a1-yandex-kit-skills/a1-yandex-kit"><img src="https://agentmods.dev/badge/mcp/ztemerbekov/a1-yandex-kit-skills/a1-yandex-kit/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/mcp/ztemerbekov/a1-yandex-kit-skills/a1-yandex-kit"><img src="https://agentmods.dev/badge/mcp/ztemerbekov/a1-yandex-kit-skills/a1-yandex-kit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
a1-yandex-kit 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 12d 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
{
"a1-yandex-kit": {
"command": "npx",
"args": [
"-y",
"mcp-yandex-kit@latest"
],
"env": {
"YANDEX_KIT_TOKEN": "${YANDEX_KIT_TOKEN:-}"
}
}
}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.
- 12d ago First seen · 12 lines scan A 2104502113ba
a1-yandex-kit is an MCP server published in the GitHub repository ztemerbekov/a1-yandex-kit-skills (2 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
marketplaces-mcp-ru
MCP servers for Wildberries and Ozon Seller APIs (schema-driven, safety-gated). Runs locally from the marketplaces-mcp-ru Python package. Needs 5 environment variables to run.
ecommerce
Product and category demand trend volume over time, with growth signals. Free key at trendsmcp.ai. Remote server at ecommerce.api.trendsmcp.ai.
buywhere-mcp
Product search, price comparison, and affiliate-ready shopping across Singapore and US retailers. Runs locally from the @buywhere/mcp-server npm package. Needs 2 environment variables to run.
stripe
Stripe's hosted MCP server: lets the agent work with customers, products, prices and payment links. Remote server at mcp.stripe.com.
tray
MCP server "tray" as configured in tray-tecnologia/tray-api-ai-plugin. Runs locally from the tray-mcp npm package. Needs 1 environment variable to run.
mcp-server
Agent-native global eSIM: buy for 193 countries, per-MB in USDT/USDC. Agents earn 20% referral. Runs locally from the @roamzy/mcp-server npm package. Needs 3 environment variables to run.