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.
npx skills add Belolipetsky/YooKassa-MCP --skill integration-plannergit clone --depth 1 https://github.com/Belolipetsky/YooKassa-MCPWrote 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/skills/belolipetsky/yookassa-mcp/integration-planner)<a href="https://agentmods.dev/skills/belolipetsky/yookassa-mcp/integration-planner"><img src="https://agentmods.dev/badge/skills/belolipetsky/yookassa-mcp/integration-planner/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/skills/belolipetsky/yookassa-mcp/integration-planner"><img src="https://agentmods.dev/badge/skills/belolipetsky/yookassa-mcp/integration-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00087 | $0.00756 |
| Opus 5 | $0.00044 | $0.00378 |
| Sonnet 5 | $0.00017 | $0.00151 |
| Haiku 4.5 | $0.00009 | $0.00076 |
Grade A, and why
integration-planner 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Планировщик интеграции ЮKassa
Результат
Подготовь исполнимый технический проект интеграции, привязанный к реальному стеку и бизнес-сценарию пользователя. Не выполняй финансовые операции через MCP.
Рабочий процесс
- Прочитай
AGENTS.md, манифесты зависимостей, серверные entrypoints, модели заказа и существующие платежные модули. - Зафиксируй подтвержденные требования: разовый или сохраненный способ оплаты, одно- или двухстадийный платеж, полный или частичный возврат, валюта, товары и услуги, схема чеков, система налогообложения, FFD/маркировка, webhook и SLA.
- Не выбирай налоговые значения за пользователя. Отметь их как требующие подтверждения бухгалтером, юристом или ответственным за ККТ.
- Вызови
yookassa_search_documentationпо релевантным темам иyookassa_api_searchпо нужным операциям. Для каждой операции возьми детали черезyookassa_api_details. - Спроектируй серверный контур. Секретный ключ никогда не должен попадать в браузер, мобильное приложение, git, логи или ответы API.
- Определи стабильный бизнес-ключ и способ хранения
Idempotence-Keyрядом с попыткой операции. Повтор одной бизнес-операции обязан использовать тот же ключ. - Опиши обработчик webhook как идемпотентный входной сигнал: быстро ответить HTTP 200, получить объект через API, проверить актуальный статус, применить допустимый переход состояния один раз.
- Построй матрицу чеков для создания, полного и частичного подтверждения, отмены и полного/частичного возврата. Используй
references/checklist.md. - Спроектируй тесты: unit, контрактные, интеграционные в тестовом магазине, повтор webhook, сетевой timeout, повтор POST, ошибки 401/403/404/422/429/5xx.
Формат ответа
Дай:
- границы и допущения;
- компоненты и ответственность каждого;
- sequence основного и ошибочного сценариев;
- таблицу состояний заказа, платежа, возврата и чека;
- контракт данных и места хранения ID/идемпотентности;
- webhook-политику;
- матрицу чеков;
- план реализации по файлам;
- критерии готовности и команды проверки;
- открытые решения с владельцем подтверждения.
What ships with it
2 files beside SKILL.md 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.
- 9d ago First seen · 45 lines · 87 tokens per session scan A 024e0189c1b4
integration-planner is a skill published in the GitHub repository Belolipetsky/YooKassa-MCP (0 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 756 once invoked, about $0.0004 per session on Opus 5. 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-01.
Other skills, from other repositories
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
tushare
A Python interface for Tushare, a financial data service that provides market and company information for stocks, funds, futures, and digital assets. It returns queried data as pandas tables.
stripe-best-practices
Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatictax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment…
pinme-uniwebpay
Use when generating, modifying, or reviewing PinMe Worker (Cloudflare Worker TypeScript) code that accepts payments through UniwebPay — payment links, products/prices, checkout sessions, payment status reads, refunds, subscriptions, or handling UniwebPay webhooks with @uniwebpay/sdk in a PinMe project.
erp-xpp
Finance and Operations X++ development lifecycle — scaffold models, author classes, custom services/APIs, and data entities, install matching SDKs, compile deployable packages, deploy packages, synchronize databases, and verify deployed artifacts. Use when the user wants to create, build, compile, package, deploy…
kalshi-api
Kalshi exchange mechanics — RSA-PSS auth, order schema, YES/NO orderbook convention, WebSocket, and endpoint surface. Market-type-agnostic shared layer for all Kalshi skills.