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-diagnosegit 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/commands/kimss-ai/kimss-python-sdk/kimss-diagnose)<a href="https://agentmods.dev/commands/kimss-ai/kimss-python-sdk/kimss-diagnose"><img src="https://agentmods.dev/badge/commands/kimss-ai/kimss-python-sdk/kimss-diagnose.svg" alt="Measured on agentmods" 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.00030 | $0.00358 |
| Opus 5 | $0.00015 | $0.00179 |
| Sonnet 5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
kimss-diagnose 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 5d 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 — diagnose integration issues
- MCP process: If tools never appear, verify
uvx/kimss-mcp-serverandKIMSS_API_KEYin MCP env; restart the MCP client. - Identity (HTTP): With the same API key,
GET https://api.kimss.ai/whoami(or staging host) should return JSON describing account/plan context — use this to confirm the key is valid and environment matchesKIMSS_BASE_URL. Do not paste full responses into logs if they contain PII. - Agent listing: SDK
client.chat-style listing is via legacy assistant list endpoints in product; for quick validation prefer a knownassistant_idfrom the user or a successfulkimss_run_agent/kimss_chatcall. - 429 credit / subscription: Map to
KimssCreditExhausted/KimssSubscriptionRequiredin SDK; advise workspace billing or wait — no tight retry loops. - 429 rate limit: Honor
Retry-After; backoff and retry. - 404 feature_disabled: Gateway feature may be off for that workspace — not fixable client-side by changing host away from canonical
api.kimss.ai/stg.kimss.ai. - 403 on mutate: Agent may be shared or key lacks scope — align with owned agents and management keys for create/update/function tools.
Reference: docs/llm-context.md.
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.
- 5d ago First seen · 17 lines · 30 tokens per session scan A 6b3f1d83e158
kimss-diagnose is a command published in the GitHub repository kimss-ai/kimss-python-sdk (1 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 358 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…
nyann:retrofit
Audit an existing repo against a profile and fix what's drifted. Unlike doctor (read-only), retrofit detects missing hooks, misconfigured gitignore, documentation gaps, and non-compliant history, then offers to remediate via bootstrap. Idempotent — safe to re-run.
nyann:diagnose
Bundle a redacted support-grade snapshot of the current nyann state (state + drift + hooks + config + prereqs) for inclusion in a bug report.
diagnose
Show current UNITARES governance state and operator-relevant diagnostics.