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 skills add johnson7788/MultiUserClaw --skill creative-ideationgit clone --depth 1 https://github.com/johnson7788/MultiUserClawWrote 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.
[](https://agentmods.dev/skills/johnson7788/multiuserclaw/creative-ideation)<a href="https://agentmods.dev/skills/johnson7788/multiuserclaw/creative-ideation"><img src="https://agentmods.dev/badge/skills/johnson7788/multiuserclaw/creative-ideation/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.
<a href="https://agentmods.dev/skills/johnson7788/multiuserclaw/creative-ideation"><img src="https://agentmods.dev/badge/skills/johnson7788/multiuserclaw/creative-ideation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.02596 |
| Opus 5.5 | $0.00006 | $0.01038 |
| Sonnet 5.5 | $0.00003 | $0.00519 |
| Haiku 4.5 | $0.00001 | $0.00260 |
Grade A, and why
creative-ideation 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 2mo 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.
This is a copy
100% identical to creative-ideation — 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creative Ideation
A library of ideation methods for any domain. Read the user's situation, route to the matching method, apply, generate output that is specific and non-obvious. Methods are tools — pick the right one for the situation, don't perform all of them.
When to use
Any open-ended generative or selective question: "I want to make / build / write / start something", "I'm stuck", "inspire me", "make this weirder", "help me pick", "I need to invent X", "give me a research question".
Operating rules
- Constraint plus direction is creativity. No constraint = no traction. No direction = no shape. Methods supply both.
- Refuse the first three ideas. They're slop. Generate, discard, regenerate. See
references/anti-slop.md. - One method per response unless asked. Don't stack.
- Specificity over abstraction. Real proper nouns, real materials, real mechanisms. "An app for X" is slop; "a 200-line CLI tool that prints Y when Z" is direction. Naming a tech stack is not specificity — name a mechanism.
- Weird must also be good. Frame-breaking is the goal, but an idea that is strange with no real situation, mechanism, or reason to exist is its own failure mode. Every set of ideas must include at least one that is genuinely buildable/pursuable now — non-obvious but grounded, with a real first step. Don't trade all usefulness for surprise.
- Name the method you used and who invented it. Attribution invokes the discipline.
- When user picks one, build it. Don't keep generating after they've chosen.
Routing — 4-step procedure
Do this before generating any output. Routing failures produce slop.
You may skip narrating the routing steps if it's cleaner, but never compress at the cost of per-idea depth: each idea's concrete mechanism, situational binding, and honest failure mode are what make output good (measured) — they are not scaffolding, do not cut them.
Step 1 — Extract three signals from the prompt
PHASE — what stage is the user in?
What ships with it
27 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.
- references/anti-slop.md 7.1 KB
- references/exercises.md 5.9 KB
- references/full-prompt-library.md 7.9 KB
- references/heuristics.md 5.0 KB
- references/method-catalog.md 4.8 KB
- references/methods/affinity-diagrams.md 4.6 KB
- references/methods/analogy-and-blending.md 5.2 KB
- references/methods/biomimicry.md 4.5 KB
- references/methods/chance-and-remix.md 3.7 KB
- references/methods/compression-progress.md 3.0 KB
- references/methods/creative-discipline.md 4.9 KB
- references/methods/defamiliarization.md 4.1 KB
- references/methods/derive-and-mapping.md 4.2 KB
- references/methods/first-principles.md 4.1 KB
- references/methods/jobs-to-be-done.md 3.9 KB
- references/methods/lateral-provocations.md 3.7 KB
- references/methods/leverage-points.md 4.6 KB
- references/methods/oblique-strategies.md 2.8 KB
- references/methods/oulipo.md 3.2 KB
- references/methods/pataphysics.md 3.8 KB
- references/methods/pattern-languages.md 4.5 KB
- references/methods/polya.md 3.5 KB
- references/methods/premortem-and-inversion.md 3.7 KB
- references/methods/scamper.md 3.5 KB
- references/methods/story-skeletons.md 6.1 KB
- references/methods/triz-principles.md 5.9 KB
- references/methods/volume-generation.md 3.8 KB
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.
- 2mo ago First seen · 178 lines · 14 tokens per session scan A b0b2a36387ec
creative-ideation is a skill published in the GitHub repository johnson7788/MultiUserClaw (329 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 2,596 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to creative-ideation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…