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-create-agentgit 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.00031 | $0.00283 |
| Opus 5 | $0.00015 | $0.00142 |
| Sonnet 5 | $0.00006 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
kimss-create-agent 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.
What it actually says
Kimss — create agent and first run
- Prerequisites: User has a Kimss API key with management scope (required for
POST /v1/agents/create/kimss_create_agent). Personal keys without management cannot create agents via API. - Collect inputs: Display name, optional model deployment id, optional instructions/metadata.
- Create: Call MCP tool
kimss_create_agentwith at leastname, or SDKclient.agents.create(...). Persist returnedassistant_id(and anythread_id/ conversation hints returned by the API). - First run: Call
kimss_run_agentwithassistant_id,message, noconversation_idyet — or SDKclient.agents.run(assistant_id, message, stream=False). - Threading: Store
conversation_idfrom the result; pass it on follow-up calls asconversation_id(MCP) / same in SDK (maps to JSONthread_id). - If 403: Key scope or agent ownership — do not retry with the same key; explain management scope or use an existing owned
assistant_id.
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.
- 2d ago First seen · 14 lines · 31 tokens per session scan A 8280a48db227
kimss-create-agent is a command published in the GitHub repository kimss-ai/kimss-python-sdk (1 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 283 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…
notify-authors
Open GitHub issues on flagged repos to notify authors before public disclosure.
wf-ads
Generate 50-100 ad copy variants from pain point research, then create renderable ad images.
rf
Alias for /router-feedback — submit feedback about router decision or model performance.