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/morodomi/dev-crew/context-reviewnpx skills add morodomi/dev-crew --skill context-reviewgit clone --depth 1 https://github.com/morodomi/dev-crewWhat 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.00130 | $0.00652 |
| Opus 5 | $0.00065 | $0.00326 |
| Sonnet 5 | $0.00026 | $0.00130 |
| Haiku 4.5 | $0.00013 | $0.00065 |
Grade A, and why
context-review 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
Context Review
security-scan結果の曖昧な項目について、ユーザーに質問して確認する対話型スキル。
Usage
/context-review # 直近のsecurity-scan結果をレビュー
/context-review ./scan-result.json # 指定ファイルをレビュー
Workflow
1. ANALYZE - security-scan結果を読み込み、曖昧な項目を抽出
2. QUESTION - 選択肢形式で1問ずつ確認
3. RESOLVE - 回答を反映して判定確定、JSON出力
Question Categories
| Category | Description | 質問例 |
|---|---|---|
| auth-intent | 認証要否の意図確認 | 「このAPIは認証不要で正しいですか?」 |
| error-handling | 例外処理の妥当性 | 「本番環境でスタックトレースは無効ですか?」 |
| data-exposure | データ露出の意図確認 | 「このレスポンスに機密情報は含まれますか?」 |
| business-logic | ビジネスロジック検証 | 「この計算ロジックは仕様通りですか?」 |
Resolution Values
| Value | Meaning | 対応 |
|---|---|---|
| excluded | 意図的、脆弱性でない | レポートから除外 |
| confirmed | 脆弱性として確定 | レポートに含める |
| needs_review | 判断保留 | 手動レビュー推奨としてマーク |
Integration
/security-scan ./src # 1. スキャン実行
/context-review # 2. コンテキストレビュー（対話型）
/attack-report # 3. レポート生成
With false-positive-filter
| スキル | 方式 | 対象 |
|---|---|---|
| false-positive-filter | パターンマッチ | 明確な誤検知 |
| context-review | ユーザー確認 | 曖昧な項目 |
Reference
詳細・質問テンプレート・出力JSON形式: reference.md
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 · 61 lines · 130 tokens per session scan A ebe1e78f1018
context-review is a skill published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 4d ago), licensed MIT. It adds 130 tokens to every session and 652 once invoked, about $0.0006 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…