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/blockcell-labs/blockcell/deep_analysisnpx skills add blockcell-labs/blockcell --skill deep_analysisgit clone --depth 1 https://github.com/blockcell-labs/blockcellWhat 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.00000 | $0.00394 |
| Opus 5 | $0.00000 | $0.00197 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
deep_analysis 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 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.
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.
What it actually says
Deep Analysis
Shared {#shared}
- 适合技术、产品、市场、战略、架构、系统性决策这类复杂问题。
- 目标不是复述概念，而是给出结构化判断、风险和可执行建议。
- 关键判断必须区分：
- 【事实】已知信息
- 【推断】基于事实的逻辑延伸
- 【假设】尚未验证但当前必须成立的前提
- 【待验证】目前缺失的信息
Prompt {#prompt}
- 如果问题边界偏大，先用 1 到 2 句话缩小分析边界，然后直接开始，不要先反问确认。
- 输出结构固定为：
- 问题定义与边界
- 背景与现状
- 核心变量拆解
- 关键矛盾与张力
- 反向论证
- 风险矩阵
- 多情景推演
- 结论与建议
- 结论部分必须包含：
- 核心判断
- 置信度
- 最大风险点
- 反转信号
- 可执行建议
- 输出标准：
- 复杂问题默认写深，不做泛泛而谈
- 至少给出 2 个反向论证
- 必须指出能推翻结论的关键变量
- 信息不足时，明确列出缺失信息，而不是用空泛语气掩盖
- 禁止：
- 教科书式定义
- “看情况”但不说明取决于什么
- 假装不确定性不存在
What ships with it
1 file 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 · 40 lines · 0 tokens per session scan A 9cb4a4fa262d
deep_analysis is a skill published in the GitHub repository blockcell-labs/blockcell (263 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 394 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-30.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.