Borrowing it
Nothing to install: this file belongs to dkanster/mailganer-api-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dkanster/mailganer-api-mcp/main/.cursor/skills/manage-api-docs/SKILL.mdgit clone --depth 1 https://github.com/dkanster/mailganer-api-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/dkanster/mailganer-api-mcp/manage-api-docs)<a href="https://agentmods.dev/skills/dkanster/mailganer-api-mcp/manage-api-docs"><img src="https://agentmods.dev/badge/skills/dkanster/mailganer-api-mcp/manage-api-docs.svg" alt="Measured on agentmods" 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.00061 | $0.00932 |
| Opus 5 | $0.00030 | $0.00466 |
| Sonnet 5 | $0.00012 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
manage-api-docs 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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Управление документацией Mailganer API
MCP-сервер mailganer-api — локальный кэш документации и live-вызовы REST API (с MAILGANER_API_KEY).
Установка
git clone https://github.com/dkanster/mailganer-api-mcp.git
cd mailganer-api-mcp
./setup.sh .
Reload MCP в Cursor: Settings → MCP → Reload.
MAILGANER_API_KEY нужен для live-вызовов API (call_mailganer_api, prepare_api_call). Для управления документацией ключ не обязателен.
POSTMAN_API_KEY нужен для MCP-сервера postman (коллекции и workspace в вашем аккаунте) и для записи в коллекцию через scripts/add-missing-postman-requests.py. Локальный кэш Postman (docs/postman/) синхронизируется из публичной коллекции и работает без ключа.
Типовые сценарии
Вызвать API
get_api_credentials_status— проверить ключprepare_api_callс slug — method, path, example bodycall_mailganer_api— выполнить запрос
Prompt call-endpoint объединяет эти шаги.
Обновить весь кэш
Инструмент sync_documentation с target: "all".
Или в терминале:
python3 scripts/sync-api-docs.py
python3 scripts/sync-postman.py
Статус кэша
get_doc_status — когда последний sync, сколько страниц, ошибки, Postman.
get_cache_health — быстрая проверка, достаточно ли docs/ для работы (после pip install без clone часто ready: false).
Найти метод
search_api_docs— по тексту страниц (параметры, примеры, заголовки)search_postman— по Postman-коллекцииget_api_endpoint_doc— страница docs вместе с Postman-запросамиget_linked_postman_request— Postman-запрос вместе со страницами docs
Проверить, изменилась ли страница на сайте
check_doc_page с slug — сравнивает кэш с live-версией и показывает diff.
«Дыры» в связях docs ↔ Postman
list_crosslink_gaps — что не связано и почему (doc_notes в docs/manual-crosslinks.json).
Ручные связи правятся в docs/manual-crosslinks.json, затем rebuild_doc_crosslinks.
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.
- 5d ago First seen · 102 lines · 61 tokens per session scan A bd226d96f221
manage-api-docs is a skill published in the GitHub repository dkanster/mailganer-api-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 932 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…