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/greglas75/zuvo/brainstormnpx skills add greglas75/zuvo --skill brainstormgit clone --depth 1 https://github.com/greglas75/zuvoWhat 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.00056 | $0.10110 |
| Opus 5 | $0.00028 | $0.05055 |
| Sonnet 5 | $0.00011 | $0.02022 |
| Haiku 4.5 | $0.00006 | $0.01011 |
Grade A, and why
brainstorm scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
[Aggregator section. Lists the proof runners required by this spec (vitest, curl, playwright, chrome-devtools MCP, etc.) and any infrastructure prerequisites (test DB, fixture files, dev server). Per-AC proof bodies live How it starts
The opening of the file, as written. The whole thing — 684 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zuvo:brainstorm
Understand the problem thoroughly. Design a solution collaboratively. Write a spec. Get approval. Only then does anything get built.
Hard Gate
Do NOT write implementation code. This skill produces a design specification document. Implementation happens later via zuvo:plan and zuvo:execute. If the user asks to "just start coding" during brainstorm, explain that the spec must be approved first — skipping design leads to rework.
Mandatory File Loading
Phase 0 — Bootstrap (load before any work)
Include paths resolve relative to THIS SKILL.md's directory (not CWD): a ../../shared/includes/ reference means <plugin-root>/shared/includes/ — never resolve it against the project being worked on.
../../shared/includes/codesift-setup.md-- CodeSift discovery and initialization../../shared/includes/env-compat.md-- Agent dispatch patterns per environment../../shared/includes/acceptance-proof-protocol.md-- Per-AC proof contract for plan/execute../../shared/includes/provided-artifact-supremacy.md-- Design-artifact supremacy (the Provided-Design Check runs BEFORE Phase 1, so this is Phase-0 mandatory, not deferred)
Deferred — Load when needed (NOT at startup)
../../rules/cq-patterns.md-- Load at Phase 3 (design decisions), NOT at Phase 0../../shared/includes/run-logger.md-- Load at completion only../../shared/includes/retrospective.md-- Load at completion only
Print the checklist:
CORE FILES LOADED:
1. codesift-setup.md -- READ
2. env-compat.md -- READ
3. acceptance-proof-protocol.md -- READ
4. provided-artifact-supremacy.md -- READ
5. cq-patterns.md -- DEFERRED (Phase 3)
6. run-logger.md -- DEFERRED (completion)
7. retrospective.md -- DEFERRED (completion)
If a Phase 0 file is missing, STOP. Deferred files are loaded when their phase begins.
Phase 0.1 — Retro checkpoint marker (run this bash at bootstrap)
What ships with it
4 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.
- 2d ago First seen · 684 lines · 56 tokens per session scan A 89be60593dd4
brainstorm is a skill published in the GitHub repository greglas75/zuvo (6 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 10,110 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ring:adopting-lib-commons-huma-wrapper
Adopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec…
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:opening-pull-requests
Open a GitHub Pull Request with automatic base branch detection, scope allowlist enforcement, PR template filling, and post-create base verification. Replaces ring:generating-pr-descriptions. Use after pushing a branch when ready to open a PR. Skip if the branch is not yet pushed or there are uncommitted changes …
ring:cleaning-comments
Cleaning redundant and obvious comments following clean code principles while preserving meaningful documentation. Supports git scope filtering (staged, unstaged, branch, commit-range). Use when code has excessive comments, during code review, or post-refactor cleanup. Skip when reviewing documentation files or…