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 manhvann/codexkit --skill scoutgit clone --depth 1 https://github.com/manhvann/codexkitWrote 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/manhvann/codexkit/scout)<a href="https://agentmods.dev/skills/manhvann/codexkit/scout"><img src="https://agentmods.dev/badge/skills/manhvann/codexkit/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/manhvann/codexkit/scout"><img src="https://agentmods.dev/badge/skills/manhvann/codexkit/scout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00743 |
| Opus 5.5 | $0.00017 | $0.00297 |
| Sonnet 5.5 | $0.00008 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00074 |
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 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 — 90 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 when available, or run parallel file reads/searches
- Collect results into concise report
Configuration
Read from .codex/.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)
- If task tools exist, check existing scout tasks first
- If not found, create one tracked task per 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:
- Mark each tracked task
in_progressbefore spawning its agent when task tools exist - 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.
- 1mo ago First seen · 90 lines · 42 tokens per session scan A fd203d859ab2
ck:scout is a skill published in the GitHub repository manhvann/codexkit (89 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 743 once invoked, about $0.0002 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…