kimss-product

kimss-product is a cursor rule for coding agents from kimss-ai/kimss-python-sdk. It costs 22 tokens per session (523 once invoked), scanned A, original, MIT.

A set of Kimss product and API rules for connecting Cursor to Kimss, a secure gateway and control system for AI agents. It covers gateway addresses, authentication, and integration conventions.

In plain words
What is it for?
Use it when connecting Cursor or Python and MCP integrations to Kimss while keeping the native OpenAI or Anthropic SDK.
Why use it?
It helps prevent incorrect connection methods, missing agent identification, and exposed API keys when integrating Kimss.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/kimss-ai/kimss-python-sdk/kimss-product
Clone the repo
git clone --depth 1 https://github.com/kimss-ai/kimss-python-sdk
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 523 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00523
Opus 5 $0.00011 $0.00262
Sonnet 5 $0.00004 $0.00105
Haiku 4.5 $0.00002 $0.00052

Measured 2d ago against content hash 9d59860a56b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

kimss-product 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 2d 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.

rules/kimss-product.mdc · 37 lines

What it actually says

Kimss — product integration (public)

What Kimss is

Kimss is a Secure AI Gateway and Governance Control Plane for autonomous agents (identity, audit trail, kill switch, provider vault). It does not host inference. Integrations should keep the native OpenAI or Anthropic SDK and point it at the dual-listener gateway, not custom chat wrappers.

Canonical hosts

  • Gateway (OpenAI): https://api.kimss.ai/v1
  • Gateway (Anthropic): https://api.kimss.ai (SDK appends /v1/messages)
  • Control-plane API root: https://api.kimss.ai (no trailing slash)
  • Staging: https://stg.kimss.ai

Authentication

  • Gateway / OpenAI or Anthropic clients: api_key=kimss_... (Bearer or x-api-key) plus X-Kimss-Agent-Id (required for attribution / JIT discovery / kill switch).
  • Control-plane KimssClient / MCP: HTTP header X-Kimss-Key. Env: KIMSS_WORKSPACE_KEY or KIMSS_API_KEY.
  • Never commit keys; never log key values.

Conventions

  • Preferred inference: keep the native SDK. OpenAI → base_url="https://api.kimss.ai/v1" (POST /v1/chat/completions). Anthropic → base_url="https://api.kimss.ai" (POST /v1/messages).
  • Deprecated: KimssClient.agents.run, chat, Agent.query, models.create, MCP kimss_chat / kimss_run_agent / kimss_complete.
  • Control plane: agents.register, usage.report; kill switch POST /agent_set_status/; audit POST /audit_log/.
  • Azure official clients are not inbound drop-ins. Vault Azure (and any backend) under Provider Vault.

Dense context

Changes

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.

  1. 2d ago First seen · 37 lines · 22 tokens per session scan A 9d59860a56b5

Subscribe to this mod's changes

kimss-product is a cursor rule published in the GitHub repository kimss-ai/kimss-python-sdk (1 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 523 once invoked, about $0.0001 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.