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 thkt/dotclaude --skill use-context-reviewer-silencegit clone --depth 1 https://github.com/thkt/dotclaudeWrote 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/thkt/dotclaude/use-context-reviewer-silence)<a href="https://agentmods.dev/skills/thkt/dotclaude/use-context-reviewer-silence"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/use-context-reviewer-silence/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/thkt/dotclaude/use-context-reviewer-silence"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/use-context-reviewer-silence.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.00047 | $0.00443 |
| Opus 5 | $0.00023 | $0.00221 |
| Sonnet 5 | $0.00009 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
use-context-reviewer-silence 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 9d 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
use-context-reviewer-silence
検出
| ID | パターン | 修正 |
|---|---|---|
| SF1 | catch (e) {} |
catch (e) { logger.error(e); throw } |
| SF1 | catch (e) { console.log(e) } |
ユーザーへのフィードバック + コンテキスト ログ |
| SF2 | .then(fn) で .catch() なし |
.catch() 追加または try/catch を使う |
| SF2 | async () => { await fn() } |
try/catch でラップしエラーを扱う |
| SF3 | エラー UI 状態なし | error boundary、フィードバック コンポーネント追加 |
| SF4 | value ?? defaultValue のサイレント |
フォールバック使用時にログ |
| SF4 | data?.nested?.value |
想定外の null をチェックして報告 |
| SF5 | catch { return defaultValue } |
デフォルトを返す前に根本原因をログ |
| SF5 | config.x || fallback |
設定をバリデーション、欠落キーは warn |
参照ファイル
検出パターンの詳細は ${CLAUDE_SKILL_DIR}/references/detection-patterns.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.
- 9d ago First seen · 30 lines · 47 tokens per session scan A 442e87257bbb
use-context-reviewer-silence is a skill published in the GitHub repository thkt/dotclaude (12 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 443 once invoked, about $0.0002 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-30.
Other skills, from other repositories
team-management-receiving-feedback
How to receive code review as technical evaluation rather than social performance — verify claims against the codebase before implementing, push back with evidence, and drop the performative agreement. Use when responding to a human reviewer, a PR comment, or another AI reviewer, and when deciding whether a suggestion…
mindforge-review
Request cross-AI peer review of phase plans from external AI CLIs.
mindforge-pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
mindforge-ship
Create PR, run review, and prepare for merge after verification passes.
review
Adversarial design review of a System Design Doc. Interrogates the staff questions, finds the cost-explosion and failure risks, returns a verdict. Sensors and evals gate.
council
Five independent critic subagents in parallel on an idea, plan, design, R&R strategy, grant, or SKILL.md, then a synthesis pass that ranks findings by how much of the argument rests on them, never by vote count. TRIGGER on "council", "spawn critics", "parallel critique", "kitchen cabinet", "panel review", "stress-test…