collision-zone-thinking

collision-zone-thinking is a skill for Codex from PracticalSwan/agent-skills. It costs 23 tokens per session (950 once invoked), scanned A, original, MIT.

A creative thinking method that combines unrelated ideas to uncover new ways to solve a problem.

In plain words
What is it for?
Use it to explore ideas for code organization, service architecture, data flow, request handling, error handling, and distributed-system reliability.
Why use it?
It gives you a structured way to get unstuck by examining a technical problem through a metaphor from another field.

Skill for Codex

Written for Codex: reads ~/.codex or $CODEX_HOME. Also seen: mentions Claude Code; mentions Codex.

Good fit Use it to explore ideas for code organization, service architecture, data flow…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/practicalswan/agent-skills/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 PracticalSwan/agent-skills --skill collision-zone-thinking
Clone the repo
git clone --depth 1 https://github.com/PracticalSwan/agent-skills

Made for: Codex.

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/practicalswan/agent-skills/collision-zone-thinking.svg)](https://agentmods.dev/skills/practicalswan/agent-skills/collision-zone-thinking)
Your own site
<a href="https://agentmods.dev/skills/practicalswan/agent-skills/collision-zone-thinking"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/collision-zone-thinking.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 950 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 original No closer match found 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.00023 $0.00950
Opus 5 $0.00012 $0.00475
Sonnet 5 $0.00005 $0.00190
Haiku 4.5 $0.00002 $0.00095

Measured today against content hash 6d4379a5551a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 today.

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.

collision-zone-thinking/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

Cross-Client Portability

Read the full file on GitHub · 111 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. today Changed 6d4379a5551a
  2. 3d ago Changed 435285cf73f9
  3. 7d ago First seen · 111 lines · 23 tokens per session scan A 3ad0f366581d

Subscribe to this mod's changes

collision-zone-thinking is a skill published in the GitHub repository PracticalSwan/agent-skills (13 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 950 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories