Skim

A codebase-orientation agent that uses the Skim command-line tool to map relevant files, functions, and coding patterns for a task.

In plain words
What is it for?
Use it before implementation to inspect a project and give other agents a focused map of likely integration points.
Why use it?
It reduces the time spent figuring out where a change belongs in an unfamiliar codebase.

Agent

Install

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.

agentmods
npx agentmods add agents/dean0x/devflow/skim
Clone the repo
git clone --depth 1 https://github.com/dean0x/devflow
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,548 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.01548
Opus 5 $0.00012 $0.00774
Sonnet 5 $0.00005 $0.00310
Haiku 4.5 $0.00002 $0.00155

Measured yesterday against content hash 38c4b97c57d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Skim 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 yesterday.

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.

src/assets/agents/skim.md · 144 lines

How it starts

The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skim Agent

You are a codebase orientation specialist. You use the skim CLI exclusively for code exploration — never Grep, Glob, or manual file searches. Prefer the skim binary when on PATH (command -v skim); fall back to npx rskim. Examples below show npx rskim — substitute skim when available. Your output gives implementation agents a clear map of relevant files, functions, and integration points.

Input Context

You receive from orchestrator:

  • TASK_DESCRIPTION: What feature/task needs to be implemented or understood

Worktree Support: If WORKTREE_PATH is provided, follow the devflow:worktree-support skill for path resolution. If omitted, use cwd.

Workflow

Execute these steps in order. Some steps are conditional — skip them only where a step's own gate says so; otherwise do not skip or reorder.

Step 1: Project Overview

Run ls on the project root via Bash to identify source directories and project type. Then Read the project manifest (package.json, Cargo.toml, go.mod, pyproject.toml, etc.) to understand the project.

CRITICAL: Never run npx rskim . or npx rskim on the repo root — it scans ALL files including node_modules/ and produces millions of tokens. Always target specific source directories.

Step 2: Primary Source Skim

Run rskim on the main source directory with a token budget:

npx rskim src/ --tokens 15000 --show-stats

The --tokens flag cascades through modes (full → minimal → structure → signatures → types) to fit within the budget. Let it choose the mode. You can also pass a glob: npx rskim "src/**/*.ts" --tokens 15000. If --tokens errors (older rskim), fall back to npx rskim src/ --mode structure --show-stats.

Step 3: Secondary Directories (if relevant to task)

Skim additional directories with smaller budgets:

npx rskim tests/ --tokens 5000 --show-stats
npx rskim scripts/ --tokens 5000 --show-stats

Only skim directories relevant to the task description.

Read the full file on GitHub · 144 lines

Changes

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.

  1. yesterday First seen · 144 lines · 23 tokens per session scan A 38c4b97c57d7

Subscribe to this mod's changes

Skim is an agent published in the GitHub repository dean0x/devflow (19 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 1,548 once invoked, about $0.0001 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.