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 agentmods add skills/kimss-ai/kimss-python-sdk/kimss-mcp-setupnpx skills add kimss-ai/kimss-python-sdk --skill kimss-mcp-setupgit clone --depth 1 https://github.com/kimss-ai/kimss-python-sdkWrote 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/kimss-ai/kimss-python-sdk/kimss-mcp-setup)<a href="https://agentmods.dev/skills/kimss-ai/kimss-python-sdk/kimss-mcp-setup"><img src="https://agentmods.dev/badge/skills/kimss-ai/kimss-python-sdk/kimss-mcp-setup.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 | $0.00040 | $0.00860 |
| Opus 5 | $0.00020 | $0.00430 |
| Sonnet 5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
kimss-mcp-setup 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 4d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kimss MCP setup
When to use
- User asks how to wire Kimss into Cursor, Windsurf, Claude Desktop, or another MCP client.
- Debugging MCP startup (missing API key, wrong base URL, tools not listed).
Requirements
uv/uvxorpip install 'kimss[mcp]'sokimss-mcp-serveris available.- Long-lived Kimss API key from the app: Developer Settings → API Keys (never commit it).
Cursor / generic mcp.json
{
"mcpServers": {
"kimss": {
"command": "uvx",
"args": ["--from", "kimss[mcp]", "kimss-mcp-server"],
"env": {
"KIMSS_API_KEY": "your_key_here",
"KIMSS_BASE_URL": "https://api.kimss.ai"
}
}
}
}
- Set
KIMSS_API_KEYin the IDE environment or user secrets — not in the repo. - Optional:
KIMSS_WORKSPACE_IDfor workspace-scoped calls. - Prefer
uvx --from kimss[mcp] kimss-mcp-server(not--with).
Claude Desktop (claude_desktop_config.json)
- Settings → Developer → Edit Config (opens the correct file for the install).
- Merge the same
kimssmcpServersblock as above. - Fully quit and relaunch Claude Desktop; confirm tools appear in the MCP/hammer UI.
Typical paths (prefer Edit Config over guessing):
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows (classic) | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
Installed package alternative
After pip install 'kimss[mcp]':
"command": "kimss-mcp-server",
"args": [],
"env": { "KIMSS_API_KEY": "...", "KIMSS_BASE_URL": "https://api.kimss.ai" }
MCP tools (v1, non-streaming)
| Tool | Backend (summary) |
|---|---|
kimss_chat |
POST /v1/agents/run |
kimss_run_agent |
POST /v1/agents/run |
kimss_create_agent |
POST /v1/agents/create (management-scoped key) |
kimss_complete |
POST /v1/models/completions |
kimss_upload_file |
POST /v1/files/upload |
kimss_add_function_to_agent |
POST /agent_add_function/ |
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.
- 4d ago First seen · 87 lines · 40 tokens per session scan A be9873fbddfe
kimss-mcp-setup is a skill published in the GitHub repository kimss-ai/kimss-python-sdk (1 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 860 once invoked, about $0.0002 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
nginx-to-higress-migration
Migrate from ingress-nginx to Higress in Kubernetes environments. Use when (1) analyzing existing ingress-nginx setup (2) reading nginx Ingress resources and ConfigMaps (3) installing Higress via helm with proper ingressClass (4) identifying unsupported nginx annotations (5) generating WASM plugins for nginx…
agent-session-monitor
Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage. Supports web interface for viewing complete conversation history and costs. Use when users ask about current session token consumption, conversation history, or cost statistics.
higress-openclaw-integration
Deploy and configure Higress AI Gateway for OpenClaw integration. Use when: (1) User wants to deploy Higress AI Gateway, (2) User wants to configure OpenClaw to use more model providers, (3) User mentions 'higress', 'ai gateway', 'model gateway', 'AI网关', (4) User wants to set up model routing or auto-routing, (5) User…
higress-daily-report
生成 Higress 项目每日报告，追踪 issue/PR 动态，沉淀问题处理经验，驱动社区问题闭环。用于生成日报、跟进 issue、记录解决方案。.
higress-wasm-go-plugin
Develop Higress WASM plugins using Go 1.24+. Use when creating, modifying, or debugging Higress gateway plugins for HTTP request/response processing, external service calls, Redis integration, or custom gateway logic.
higress-auto-router
Configure automatic model routing using the get-ai-gateway.sh CLI tool for Higress AI Gateway. Use when: (1) User wants to configure automatic model routing, (2) User mentions 'route to', 'switch model', 'use model when', 'auto routing', (3) User describes scenarios that should trigger specific models, (4) User wants…