Kimi K2.6 vs Claude Opus 4.7: A Practical Coding Showdown on a Minetest Mod + Google Sheets Integration

What's the test?

A developer compared Kimi K2.6 and Claude Opus 4.7 on a two-part coding task: building a Minetest/Luanti bounty board game mod with a TypeScript backend, then extending it with Google Sheets logging through Composio. Both models got identical prompts and were measured on working result, code quality, debugging pain, time, token usage, and cost.

Setup: Claude Opus 4.7 via Claude Code, Kimi K2.6 via OpenCode on OpenRouter. Same repo, same success criteria.

Test 1: Local bounty board

Claude Opus 4.7 built an Express/Zod/Vitest backend, Lua mod, /bounty flow, rewards, and leaderboard with passing tests.

• Cost: ~$3.59
• Time: 12 min API, 23 min wall
• Code: +1,688 / -0
• Output: 54.8k tokens
• Cache read: 2.8M tokens

Kimi K2.6 also got the local bounty board working — backend routes, Lua mod, basic game flow — but the code was messier. It wrote secure.http_mods = bountykimi in the global config, but also created a world-level config with a different mod name, so the HTTP API wasn't enabled for the actual running mod. Debugging took 30+ minutes.

• Cost: ~$0.39
• Duration: ~9 min 27 sec
• Code changes: +4,671 / -0 (2.7x more than Opus)
• Context used: 52,073 tokens
• Context window: 20%

Verdict: Both passed Test 1, but Opus's output was cleaner and smaller.

Test 2: Composio + Google Sheets

Claude Opus 4.7 got the Google Sheets sync working after some back-and-forth on tsx watch and env loading. The backend could complete a bounty and append to Google Sheets through Composio.

• Cost: $16.03 (painful)
• Time: 28 min API, 1 hr 17 min wall
• Code: +1,848 / -507
• Cache read: 22.3M tokens
• Output: 123.3k tokens

Kimi K2.6 failed. It got stuck on dev server issues, tests, and build problems, and never wired the Composio integration into a clean working state. After ~25 minutes and 135k+ tokens, the test was stopped.

• Cost: ~$5.03
• Time: ~25 min
• Tokens: 135k+

Key takeaways

• Best local MVP: Opus (cleaner), but Kimi is far better value.
• Best real integration: Opus by a large margin.
• Cleaner code: Opus (1.7k vs 4.7k lines for the same task).
• Cheapest experiment model: Kimi K2.6.
• Most painful cost: Opus ($16 for Google Sheets sync).

Kimi K2.6 is interesting for cheap local coding tasks — $0.39 for a working Lua + TypeScript mod is impressive. But when external tools, config issues, and real integration are involved, Opus 4.7 remains clearly ahead.