Collision-Zone Thinking

Collision-Zone Thinking is a skill for Claude Code from VoDaiLocz/kilo-kit-mcp. It costs 24 tokens per session (448 once invoked), scanned A, a copy of Collision-Zone Thinking, Apache-2.0.

A creative problem-solving exercise that combines unrelated ideas to find new ways of understanding a technical problem.

In plain words
What is it for?
Use it during architecture discussions, debugging, and design work to explore metaphors and test whether they reveal practical solutions.
Why use it?
It helps generate alternatives when ordinary ways of organizing code, services, data, or error handling are not producing useful ideas.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Good fit Use it during architecture discussions, debugging, and design work to explore metaphors and test whether they reveal practical solutions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vodailocz/kilo-kit-mcp/collision-zone-thinking
Install

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.

Any agent
npx skills add VoDaiLocz/kilo-kit-mcp --skill collision-zone-thinking
Clone the repo
git clone --depth 1 https://github.com/VoDaiLocz/kilo-kit-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for Collision-Zone Thinking

README.md
[![agentmods](https://agentmods.dev/badge/skills/vodailocz/kilo-kit-mcp/collision-zone-thinking/github.svg)](https://agentmods.dev/skills/vodailocz/kilo-kit-mcp/collision-zone-thinking)
Your own site
<a href="https://agentmods.dev/skills/vodailocz/kilo-kit-mcp/collision-zone-thinking"><img src="https://agentmods.dev/badge/skills/vodailocz/kilo-kit-mcp/collision-zone-thinking/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Collision-Zone Thinking

Your own site · 80×15
<a href="https://agentmods.dev/skills/vodailocz/kilo-kit-mcp/collision-zone-thinking"><img src="https://agentmods.dev/badge/skills/vodailocz/kilo-kit-mcp/collision-zone-thinking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 448 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00448
Opus 5 $0.00012 $0.00224
Sonnet 5 $0.00005 $0.00090
Haiku 4.5 $0.00002 $0.00045

Measured 6d ago against content hash 416850bf47da, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

Collision-Zone Thinking 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 6d 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.

Origin

This is a copy

100% identical to Collision-Zone Thinking — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/problem-solving/collision-zone-thinking/SKILL.md · 63 lines

What it actually says

Collision-Zone Thinking

Overview

Revolutionary insights come from forcing unrelated concepts to collide. Treat X like Y and see what emerges.

Core principle: Deliberate metaphor-mixing generates novel solutions.

Quick Reference

Stuck On Try Treating As Might Discover
Code organization DNA/genetics Mutation testing, evolutionary algorithms
Service architecture Lego bricks Composable microservices, plug-and-play
Data management Water flow Streaming, data lakes, flow-based systems
Request handling Postal mail Message queues, async processing
Error handling Circuit breakers Fault isolation, graceful degradation

Process

  1. Pick two unrelated concepts from different domains
  2. Force combination: "What if we treated [A] like [B]?"
  3. Explore emergent properties: What new capabilities appear?
  4. Test boundaries: Where does the metaphor break?
  5. Extract insight: What did we learn?

Example Collision

Problem: Complex distributed system with cascading failures

Collision: "What if we treated services like electrical circuits?"

Emergent properties:

  • Circuit breakers (disconnect on overload)
  • Fuses (one-time failure protection)
  • Ground faults (error isolation)
  • Load balancing (current distribution)

Where it works: Preventing cascade failures Where it breaks: Circuits don't have retry logic Insight gained: Failure isolation patterns from electrical engineering

Red Flags You Need This

  • "I've tried everything in this domain"
  • Solutions feel incremental, not breakthrough
  • Stuck in conventional thinking
  • Need innovation, not optimization

Remember

  • Wild combinations often yield best insights
  • Test metaphor boundaries rigorously
  • Document even failed collisions (they teach)
  • Best source domains: physics, biology, economics, psychology
Changes

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.

  1. 6d ago First seen · 63 lines · 24 tokens per session scan A 416850bf47da

Subscribe to this mod's changes

Collision-Zone Thinking is a skill published in the GitHub repository VoDaiLocz/kilo-kit-mcp (26 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 448 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Collision-Zone Thinking, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories