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 commands/kimss-ai/kimss-python-sdk/kimss-setupgit clone --depth 1 https://github.com/kimss-ai/kimss-python-sdkWhat 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.00033 | $0.00308 |
| Opus 5 | $0.00016 | $0.00154 |
| Sonnet 5 | $0.00007 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
kimss-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 yesterday.
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 MCP setup check
- Confirm transport: User should have
uvxon PATH, orkimss-mcp-serverafterpip install 'kimss[mcp]'. - Confirm env:
KIMSS_API_KEYis set in the MCP server environment (never in repo). OptionalKIMSS_BASE_URL(https://api.kimss.aiorhttps://stg.kimss.ai). OptionalKIMSS_WORKSPACE_IDfor workspace scoping. - Confirm config location: Cursor uses project or user MCP config; this repo ships root
mcp.jsonas a reference template — merge thekimssblock into the user’s effective MCP config if they are not loading repo-level MCP automatically. - Smoke test (after MCP is running): Invoke
kimss_run_agentwith a validassistant_idthe user owns and a shortmessage; captureconversation_idfor a second turn. If no agent id yet, usekimss_create_agentonly if their key has management scope. - If startup fails: Read stderr for
KIMSS_API_KEY; see docs/llm-context.md error table for HTTP-layer issues.
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.
- yesterday First seen · 13 lines · 33 tokens per session scan A d4c6732799cf
kimss-setup is a command published in the GitHub repository kimss-ai/kimss-python-sdk (1 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 308 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 commands, from other repositories
Issue Spec: Apply
Implement directly or use an optional PROCESS when managed coordination is required.
Issue Spec: Propose
Create or continue proposal, SPEC, QUESTION, design, and TASK artifacts for an issue-spec change.
gen-agent
You are a specialized prompt engineer tasked with generating high-quality, structured prompts for AI agents based on user descriptions. Your goal is to create agent prompts that follow a consistent format inspired by subagent creation workflows, similar to Claude's structured agent design. When you receive an input in…
scan-skill
Scan a specific MCP skill by npm package name or GitHub URL.
wf-ads
Generate 50-100 ad copy variants from pain point research, then create renderable ad images.
router-feedback
Submit feedback about router decision or model performance.