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-cli-scoutgit 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-cli-scout)<a href="https://agentmods.dev/skills/thkt/dotclaude/use-cli-scout"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/use-cli-scout/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-cli-scout"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/use-cli-scout.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.00033 | $0.00975 |
| Opus 5.5 | $0.00013 | $0.00390 |
| Sonnet 5.5 | $0.00007 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
use-cli-scout 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
use-cli-scout
使いどころ
Web 上の情報が要るときは scout を使う。ページの本文がそのまま返るので、一次ソースを直接読んで答えられる。入力に http:// または https:// の URL があれば、答える前に取得する。
コマンド
URL を渡されたら
repo-overview と repo-read は完全な URL と owner/repo のどちらでも受け付ける。Slack permalink は fetch が判別して Slack Web API へ回す。
| URL の形 | コマンド |
|---|---|
github.com/<owner>/<repo> |
scout repo-overview <url> |
github.com/<owner>/<repo>/blob/<ref>/<path> |
scout repo-read <owner/repo> <path> |
| それ以外 (Slack permalink を含む) | scout fetch <url> |
調べる
-l ja と -l en で検索言語を固定する (既定は auto)。JS 描画が要るページには --js、抽出前のページ全体には --raw を付ける。
| 欲しいもの | コマンド | 返るもの |
|---|---|---|
| 情報源の候補 | scout search "query" |
1 行 1 URL |
| トピックの本文一式 | scout research "topic" -d <1-10> |
上位 N 件を取得した Markdown レポート |
| 1 ページの本文 | scout fetch <url> |
本文抽出済みの Markdown |
GitHub を辿る
--ref で branch、tag、commit SHA を指定する。
| 段階 | コマンド |
|---|---|
| repo の全体像 (説明、issue、PR、release、README) | scout repo-overview <owner/repo> |
| ファイル構成 | scout repo-tree <owner/repo> [-p <dir>] [--pattern '*.rs'] |
| ファイルの中身 | scout repo-read <owner/repo> <path> [-l 1-80] |
前提
| 環境変数 | 無いとどうなるか |
|---|---|
SLACK_TOKEN |
Slack permalink の取得が失敗する |
GITHUB_TOKEN |
GitHub のレート上限が下がる。取得自体は通る |
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 Changed 8d7499e7f420
- 1mo ago First seen · 61 lines · 33 tokens per session scan A 063d298d9926
use-cli-scout is a skill published in the GitHub repository thkt/dotclaude (12 stars, last pushed 25d ago), licensed MIT. It adds 33 tokens to every session and 975 once invoked, about $0.0001 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-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…
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. A markdown work plan gets the plan roster (assumptions, pre-mortem, what to delete, alternatives per piece…
pr-reviewer
Review pull requests with full context. Fetches linked Jira tickets, Figma designs, and Notion docs via MCP, spawns parallel subagents for systematic code review (correctness, security, tests, SOLID, clean code), then drafts friendly, humanized GitHub-ready comments. Use when reviewing PRs, examining code changes, or…
implementation-review
Pre-commit quality gate. Invoke before every git commit, after /flagrare:staleness-audit. Seven checks, plan gaps, use-case coverage gaps, missing test scenarios, test philosophy violations (Kent Dodds Testing Trophy), SOLID violations, Clean Code violations, and security vulnerabilities. Each check is delegated to a…
security-audit
Focused security review of a change. Finds HIGH-CONFIDENCE, concretely exploitable vulnerabilities in the staged diff (injection, broken authn/authz, secrets and data exposure, unsafe deserialization, crypto misuse, SSRF) and audits dependencies when a lockfile moved, using the repo's own package manager. Runs as…