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 bestagentkits/ck-skills --skill scoutgit clone --depth 1 https://github.com/bestagentkits/ck-skillsWrote 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/bestagentkits/ck-skills/scout)<a href="https://agentmods.dev/skills/bestagentkits/ck-skills/scout"><img src="https://agentmods.dev/badge/skills/bestagentkits/ck-skills/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/bestagentkits/ck-skills/scout"><img src="https://agentmods.dev/badge/skills/bestagentkits/ck-skills/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.00042 | $0.00797 |
| Opus 5 | $0.00021 | $0.00398 |
| Sonnet 5 | $0.00008 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
ck: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 10d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scout
Fast, token-efficient codebase scouting using parallel agents to find files needed for tasks.
Arguments
- Default: Scout using built-in Explore subagents in parallel (
./references/internal-scouting.md) ext: Scout using external Gemini/OpenCode CLI tools in parallel (./references/external-scouting.md)
When to Use
- Beginning work on feature spanning multiple directories
- User mentions needing to "find", "locate", or "search for" files
- Starting debugging session requiring file relationships understanding
- User asks about project structure or where functionality lives
- Before changes that might affect multiple codebase parts
Quick Start
- Analyze user prompt to identify search targets
- Use a wide range of Grep and Glob patterns to find relevant files and estimate scale of the codebase
- Spawn parallel agents with divided directories
- Collect results into concise report
Configuration
Read from .claude/.ck.json:
gemini.model- Gemini model (default:gemini-3-flash-preview)
Workflow
1. Analyze Task
- Parse user prompt for search targets
- Identify key directories, patterns, file types, lines of code
- Determine optimal SCALE value of subagents to spawn
2. Divide and Conquer
- Split codebase into logical segments per agent
- Assign each agent specific directories or patterns
- Ensure no overlap, maximize coverage
3. Register Scout Tasks
- Skip if: Agent count ≤ 2 (overhead exceeds benefit)
- Skip if: Task tools unavailable (VSCode extension) — use
TodoWriteinstead TaskListfirst — check for existing scout tasks in session- If not found,
TaskCreateper agent with scope metadata - See
references/task-management-scouting.mdfor patterns and examples
4. Spawn Parallel Agents
Load appropriate reference based on decision tree:
- Internal (Default):
references/internal-scouting.md(Explore subagents) - External:
references/external-scouting.md(Gemini/OpenCode)
Notes:
TaskUpdateeach task toin_progressbefore spawning its agent (skip if Task tools unavailable)- Prompt detailed instructions for each subagent with exact directories or files it should read
- Remember that each subagent has less than 200K tokens of context window
- Amount of subagents to-be-spawned depends on the current system resources available and amount of files to be scanned
- Each subagent must return a detailed summary report to a main agent
What ships with it
3 files 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.
- 10d ago First seen · 95 lines · 42 tokens per session scan A 19b960afaf35
ck:scout is a skill published in the GitHub repository bestagentkits/ck-skills (6 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 797 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-31.
Other skills, from other repositories
adr
Use when the user knows what they want built and says "/adr", "write an ADR for X", "decide and build X", or "ADR-driven". Turns an intent into a grounded, cited, build-ready ADR at docs/adr/YYYY-MM-DD- .md — load-bearing decisions surfaced to the human — then hands off to nightshift:plan's landing step (the plan is…
plan
Use when the user has an idea, feature, or fix that is more than a one-sitting edit and says "plan this", "write a plan for X", "/nightshift:plan", or "what would it take to build X". Sizes the work (trivial → no artifact; medium → a lean plan; large → a short spec first), asks one question at a time until the design…
watch
Use when a Nightwatch spec queue is about to run, or is already running, and someone needs to fire it, watch it, and steer it — "launch nightwatch", "watch the run", "/nightwatch:watch", "pause it", "skip that spec". Runs preflight, launches run.sh, arms the journal and workflow-journal monitors, knows what is safe to…
domain-modeling
Use when pinning down domain terminology, building a ubiquitous language or project glossary, disambiguating overloaded or vague terms, or maintaining a CONTEXT.md — or when another skill needs to sharpen the domain model. Do NOT use for recording architectural decisions (use adr) or for writing implementation specs.
morning
Use when the user says "/nightshift:morning", "what happened overnight", "how did the night go", "why did the loop stop", or opens a session in a repo with a loop/ directory after a scheduled run. Reads the journal since the last start line and every open land / land:blocked pull request, says per stop what happened…
writing-artifacts
Use when writing or revising a durable written artifact — README, ADR, design doc, PR description, release notes, runbook, error message, user-facing docs. Gives a positive writing system (reader model, sentence positions, document jobs), not a ban-list. Do NOT use for conversational replies to the user (global…