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/sdcorejs/sdcorejs-agent/sdcorejs-brainstormingnpx skills add sdcorejs/sdcorejs-agent --skill sdcorejs-brainstorminggit clone --depth 1 https://github.com/sdcorejs/sdcorejs-agentWrote 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/sdcorejs/sdcorejs-agent/sdcorejs-brainstorming)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-brainstorming"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-brainstorming.svg" alt="Measured on agentmods" 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 | $0.00103 | $0.05140 |
| Opus 5 | $0.00051 | $0.02570 |
| Sonnet 5 | $0.00021 | $0.01028 |
| Haiku 4.5 | $0.00010 | $0.00514 |
Grade A, and why
sdcorejs-brainstorming 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 4d 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 — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
01 - Brainstorming
Shared Protocols
Read _refs/shared/runtime-protocols.md. Load project context, choice, or
visual references only when the current question requires them. Resolve track,
stack profile, repository role, and artifact kinds from the versioned
_refs/shared/system-registry.json; do not maintain a local competing enum.
Read _refs/shared/decision-coverage.md and preserve stable requirement,
acceptance-criterion, assumption, decision, and invariant identities. Validate
the graph at the discovery stage: future task/evidence mappings remain
explicit future_gaps, while malformed identities, dangling references, and
blocking assumptions remain blockers.
Purpose
Turn a request into a confirmed requirement contract. This skill now owns both jobs that used to be split:
- Explore options when the direction is still open.
- Confirm the blocking inputs needed before
sdcorejs-spec.
Output dialogue only. Do not write specs, plans, or code here.
Process
0. Detect execution context
Detect the target project root, target_root_kind, track, and
stack_profile before asking blockers. Target-root discovery locates evidence;
it does not establish artifact ownership. Use _refs/shared/project-context.md
with:
caller_context: sdcorejs-brainstorming
context_mode: summary-read | code-map-readonly
side_effects_allowed: false
Use summary-read or code-map-readonly by default. If the summary is missing,
stale, or contradictory, keep reading targeted files; missing context is not
permission to write .sdcorejs/summary.md. Never use summary-refresh from
brainstorming unless the user explicitly approves a context write and the
authoring-repo guard says the target can be written.
TARGET_ROOT=$(git rev-parse --show-toplevel)
cd "$TARGET_ROOT"
If multiple app roots exist, ask the user which root to target with a numbered
list and short aliases from _refs/shared/user-choice-prompt.md. If no known
stack is detected, resolve it through the general generic-harness fallback in
the central registry.
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.
- 4d ago First seen · 497 lines · 103 tokens per session scan A 11f2f0d5c03d
sdcorejs-brainstorming is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 17d ago), licensed MIT. It adds 103 tokens to every session and 5,140 once invoked, about $0.0005 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…