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.
git 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/rules/kimss-ai/kimss-python-sdk/architecture-vault)<a href="https://agentmods.dev/rules/kimss-ai/kimss-python-sdk/architecture-vault"><img src="https://agentmods.dev/badge/rules/kimss-ai/kimss-python-sdk/architecture-vault/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/rules/kimss-ai/kimss-python-sdk/architecture-vault"><img src="https://agentmods.dev/badge/rules/kimss-ai/kimss-python-sdk/architecture-vault.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.00292 | $0.00292 |
| Opus 5.5 | $0.00117 | $0.00117 |
| Sonnet 5.5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
architecture-vault 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 1mo 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.
What it actually says
Kimss SDK — mirror and coverage
Source of truth: this directory lives under private monorepo kimssApi/kimss_sdk/. The public kimss-python-sdk repo is a git subtree force-push mirror. Never treat the public main as an editable SSOT.
Cross-repo notes (local): C:\projects\kimss-docs → architecture/sdk-overview.md, api/sdk-coverage.md.
Conventions
- Prefer OpenAI gateway:
base_url=https://api.kimss.ai/v1+X-Kimss-Agent-Id(see AI_INTEGRATION.md). client.agents.run/chat/models.createare deprecated for inference.- Public SDK param name:
conversation_id(v2) on residual agent APIs. - Canonical host:
https://api.kimss.ai. Auth:X-Kimss-Keyor Bearer on/v1. - Dense HTTP map in-package:
docs/llm-context.md. - Platform/DB/backoffice architecture is not this package’s job — use kimss-docs / kimssApi
cursor_application_docs/.
When changing client routes
Update vault api/sdk-coverage.md and keep docs/llm-context.md in sync in the same monorepo change.
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.
- 1mo ago First seen · 19 lines · 292 tokens per session scan A cbccf07fbf5a
architecture-vault is a cursor rule published in the GitHub repository kimss-ai/kimss-python-sdk (1 stars, last pushed 4d ago), licensed MIT. It adds 292 tokens to every session, about $0.0012 per session on Opus 5.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 cursor rules, from other repositories
plugin-development
Plugin Development Standards - Applies to all new wasm and golang-filter plugins.
windsurfrules
Create detailed components with these requirements.
reachai-project
ReachAI project rules for AI coding agents.
release-compat-policy
1.0 GA — backward compatibility for shipped contracts; greenfield for internal-only code.
worktree-per-session
Each parallel Claude Code / Cursor session runs in its own git worktree under ./worktrees/.
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.