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 skills/danium/lateral-thinking/provocationnpx skills add danium/lateral-thinking --skill provocationgit clone --depth 1 https://github.com/danium/lateral-thinkingWhat 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 | $0.00119 | $0.01554 |
| Opus 5 | $0.00060 | $0.00777 |
| Sonnet 5 | $0.00024 | $0.00311 |
| Haiku 4.5 | $0.00012 | $0.00155 |
Grade A, and why
provocation 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Provocation (Po)
What this technique does
State something deliberately wrong, impossible, or absurd about the problem — then refuse to judge it. Instead, ask what useful movement the statement creates: the principle hiding inside it, what would happen moment-to-moment if it were true, what that makes different from today. The absurd statement is not a proposal; it is a stepping stone you stand on only long enough to reach somewhere you could not have walked to directly. It works because judgment and movement are opposite mental motions, and every honest constraint you carry is also a wall you have stopped seeing.
Source: Edward de Bono, Po: Beyond Yes and No (1972) and Serious Creativity (1992).
Workflow
Step 1: Confirm the target
A valid target is a concrete creative problem where the usual answers have gone stale: a design that keeps converging on the same shape, a constraint everyone treats as physics, a process nobody questions anymore. Good phrasings: "reinvent how we onboard new users", "our pricing page always ends up looking identical to competitors", "the approval step feels untouchable — challenge it". If the target is unclear, ask one focused question — "What's the problem, and which constraint or convention feels most fixed?"
Refuse requests to perform analytical work — debugging, reviewing code, implementing a change — and suggest an analytical approach instead. Redesigning or ideating about such a process is a valid creative target: "reinvent our code-review ritual" is in scope; "review this PR" is not.
Step 2: Surface the rules
List 4–6 operating rules or constraints that everyone treats as fixed about the target. Write them as flat declaratives, not questions — the things so obvious nobody says them out loud. These are the walls. Each one is a candidate to break, invert, or exaggerate in the next step. If you cannot name at least four, the target is probably too vague; go back to Step 1.
Step 3: Generate 4–6 provocations
What ships with it
2 files 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.
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.
- yesterday First seen · 80 lines · 119 tokens per session scan A 244d215d6e72
provocation is a skill published in the GitHub repository danium/lateral-thinking (281 stars, last pushed 1mo ago), licensed MIT. It adds 119 tokens to every session and 1,554 once invoked, about $0.0006 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.
Other skills, from other repositories
creative-ideation
Structured brainstorming sessions using proven ideation techniques.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when starting from a vague idea, brainstorming a new feature, exploring design space, or stress-testing a plan before committing. Trigger phrases: "ideate", "refine this idea", "stress-test my plan", "ideate on".
idea-generator
Use when the user asks for an idea generator, conceptual crossbreeding, mutation, evolution, recombination of existing ideas, or novel concepts derived from unlike sources; also use for follow-ups that evolve, cross, or lock elements of previously generated ideas. Do not trigger for generic brainstorming with no…
brainstorming
Creative ideation and structured brainstorming with multiple methodologies.
skill-ideation
Generate agent skill ideas through problem-driven brainstorming. Situation-specific, narrow-but-universal. Triggers when user wants skill ideas or needs to expand their skill collection.
weaver-mind
Cross-domain bridge thinking for stuck founders, creators, and builders. Finds pattern bridges from unrelated fields — biology, game design, physics, jazz, architecture, logistics — and maps them to your situation with explicit reasoning, pros/cons, and a first experiment. Use when stuck, plateaued, can't get…