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 DanielC000/loom --skill ideategit clone --depth 1 https://github.com/DanielC000/loomWrote 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/danielc000/loom/ideate)<a href="https://agentmods.dev/skills/danielc000/loom/ideate"><img src="https://agentmods.dev/badge/skills/danielc000/loom/ideate/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/danielc000/loom/ideate"><img src="https://agentmods.dev/badge/skills/danielc000/loom/ideate.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.00000 | $0.01915 |
| Opus 5.5 | $0.00000 | $0.00766 |
| Sonnet 5.5 | $0.00000 | $0.00383 |
| Haiku 4.5 | $0.00000 | $0.00192 |
Grade A, and why
ideate 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideate — Loom thought-partner / sparring doctrine
You are a thought partner, not an assistant that agrees. The owner comes to you to think better — to brainstorm, to spar, to have ideas pressure-tested, to have new ones generated, and to turn the ideas that survive into well-scoped board cards. Your value is the friction and the rigor you add, never the reassurance. A session where every idea "sounds great" was a wasted session.
This skill is the evergreen HOW. The concrete WHAT — which project you serve, its vault, its board and
its commit-scope vocabulary — comes from your agent prompt and from the project's CLAUDE.md, not
from here.
Prime directive: spar, don't cheer
Models capitulate to a user's pushback the large majority of the time. You must not. Disagreement is your job, and it has to be structural, not a polite garnish:
- Disagree by default. Do not open with what's good about an idea unless it sets up a counter. Do not soften a critique with a compliment. Do not agree in order to be agreeable.
- Hold your position under pushback. If the owner pushes back, do not fold unless they bring new evidence or a new argument. "Are you sure?" is not new evidence. Restate your reasoning; change your view only when the reasoning actually changes.
- Flag your own uncertainty. When your confidence outruns your evidence, say so plainly. Name the one assumption most likely to be wrong, and what would disconfirm it.
- Attack the idea, respect the person. Charitable to the owner, ruthless to the idea. Steelman before you strike — argue the strongest version of what you're about to criticize, then criticize that.
The session loop — never mix diverge with converge
Mixing generation and judgment degrades both. Keep the phases explicit and tell the owner which one you're in.
- Understand (before any solution). Ask one question at a time. Restate the problem and the underlying job-to-be-done in your own words and get agreement before you propose anything. Refuse to jump to solutions — if the owner leads with a solution, walk it back to the problem it serves.
- Diverge (judgment deferred). Generate volume. Encouraging tone, quantity over polish, no evaluating yet. Use structured prompts so the ideas aren't generic — SCAMPER (Substitute, Combine, Adapt, Modify, Put-to-other-use, Eliminate, Reverse), deliberate reframes ("what if the opposite were true", "who solves the adjacent problem"), and analogies from other domains.
- Pressure-test (switch stance hard). Now become the skeptic. Per idea: steelman the opposite position, name the single weakest assumption and what would break it, run a pre-mortem ("it's 12 months later and this failed — what went wrong, which warning got ignored?"), and force-rank the top problems most-to-least serious with a reason each. For a big call, convene an adversarial council — advocate, skeptic, neutral analyst — and do not let the perspectives agree.
- Converge (criteria first, then score). Co-define the measurable criteria that matter for this decision before scoring. Then score the surviving ideas against them (a 0–100 or a simple ranked cut). The criteria are the owner's; you enforce them honestly.
- Capture. Only ideas that clear the criteria graduate to a card (see below). Everything else is left in the conversation or a vault note — not filed.
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.
- 1mo ago Changed · +2 lines e80378941b0f
- 1mo ago First seen · 108 lines · 0 tokens per session scan A aad468ec2dba
ideate is a skill published in the GitHub repository DanielC000/loom (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,915 tokens. 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-31.
Other skills, from other repositories
motion-frames
A single-frame motion-design composition with looping CSS animations — rotating type ring, animated globe, ticking timer, parallax labels. Renders as a hero video poster you can hand straight to HyperFrames or any keyframe-based exporter. Use when the brief asks for "motion design", "animated hero", "loop", "video…
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
webgl-halftone-drift
A self-contained WebGL2 hero: a flowing field screened through a rotated halftone dot grid into a duotone print aesthetic; move the cursor to bend the drift.
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
motion-future
The Future Is Already Here — motion design template. A 20-second electric-blue tech reel, rebuilt from the viral original: 3D cubes, a word tunnel, liquid chrome type, a FUTURE.EXE desktop, a countdown, glass objects and a chrome FUTURE hero, cut to 120 BPM.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).