cursorrules

A project rule that tells the coding agent to follow an AI_INTEGRATION.md file. The file contains instructions for using the Kimss Python SDK and gateway.

In plain words
What is it for?
Building or editing Kimss integrations while preserving the app's existing OpenAI or Anthropic SDK usage, gateway settings, agent headers, and disable switch.
Why use it?
It keeps changes consistent with the project's integration instructions and prevents the agent from using the wrong client or missing required request details.

Cursor rule for Cursor

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/cursorrules
Clone the repo
git clone --depth 1 https://github.com/kimss-ai/kimss-python-sdk

Made for: Cursor.

Per session 142 This file is loaded in full into every session.
When invoked 142 The same file — it is already loaded in full.
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.00142 $0.00142
Opus 5 $0.00071 $0.00071
Sonnet 5 $0.00028 $0.00028
Haiku 4.5 $0.00014 $0.00014

Measured today against content hash fead17ebea19, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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 today.

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.

.cursorrules · 11 lines

What it actually says

Kimss Python SDK — AI assistants

Follow AI_INTEGRATION.md.

  1. Never use KimssClient for chat/completions/messages.
  2. Keep the developer's native openai or anthropic SDK.
  3. OpenAI → base_url=https://api.kimss.ai/v1. Anthropic → base_url=https://api.kimss.ai.
  4. Always inject X-Kimss-Agent-Id (and X-Kimss-Agent-Name).
  5. Hermis: forward Agent-Id headers.
  6. Kill switch: agent_disabled. Keys: kimss_....
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. today First seen · 11 lines · 142 tokens per session scan A fead17ebea19

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository kimss-ai/kimss-python-sdk (1 stars, last pushed 2d ago), licensed MIT. It adds 142 tokens to every session, about $0.0007 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.