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 morodomi/dev-crew --skill context-reviewgit clone --depth 1 https://github.com/morodomi/dev-crewWrote 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/morodomi/dev-crew/context-review)<a href="https://agentmods.dev/skills/morodomi/dev-crew/context-review"><img src="https://agentmods.dev/badge/skills/morodomi/dev-crew/context-review/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/morodomi/dev-crew/context-review"><img src="https://agentmods.dev/badge/skills/morodomi/dev-crew/context-review.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.00130 | $0.00652 |
| Opus 5.5 | $0.00052 | $0.00261 |
| Sonnet 5.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 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.
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.
- 1mo 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 today), licensed MIT. It adds 130 tokens to every session and 652 once invoked, about $0.0005 per session on Opus 5.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
git-workflow
Perform requested Git actions while preserving user work. Triggers on "commit", "提交".
documentation-audit
Documentation review that compares five formal project documents—PRD, TECH, API, FLOW, and TODO—with the current code. It records mismatches and brings the documents back in line with reality.
ci-cd
A collection of practices for automating software checks and delivery. CI/CD means continuous integration and continuous delivery: changes are automatically checked, built, and potentially deployed.
ai-development-guide
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
recipe-review
Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved corrections.