by Lolner95 · Agent Tool · ★ 67
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
git clone https://github.com/Lolner95/use-kimi-on-cursor.gitTaken from the project's README on GitHub.
None of the 42 rules matched — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against 42 published rules built on the SlowMist agent-security taxonomy, refreshed every 8 hours.
The quality score combines nine heuristic checks of the repo and its README: completeness, clarity, specificity, examples, structure, agent readiness, step-by-step content, instruction quality and security notes. It rates how well the project explains itself to an agent, not the code.
| Stars | 67 |
| Forks | 8 |
| Language | Rust |
| Category | Agent Tool |
| License | MIT |
| Quality Score | 71/100 |
| Open Issues | 1 |
| Last Updated | 2026-06-16 |
| Created | 2026-06-09 |
| Platforms | rust |
| Est. Tokens | ~24k |
use-kimi-on-cursor Use Moonshot Kimi (K2.7 / K2.6) inside Cursor, without fighting proxies, tunnels, or broken tool calls. Quick start · How it works · Cursor setup · FAQ · Build from source The problem You want Kimi in Cursor. Sounds simple. In practice you hit walls fast: Works until it doesn't, tool names break, streaming mismat
These tools work well together with use-kimi-on-cursor for enhanced workflows:
Explore other popular agent tool tools:
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy: 42 published rules, covering credential harvesting, data exfiltration, curl | sh installers and more. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: