smith-navigate

A read-only file navigator for Smith projects. It reads Smith’s precomputed project manifest—a list describing the project’s files and systems—and returns files that are essential, useful, or merely reference material for a task.

In plain words
What is it for?
Use it with a task description to locate the files and system notes most likely to matter. It can be run directly or used by Smith’s context-loading hook.
Why use it?
It helps an agent find relevant project context without scanning the whole codebase. This can reduce unnecessary file reading before work begins.

Skill for Claude CodeCodex

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 skills/attckdigital/smith/smith-navigate
Any agent
npx skills add ATTCKDigital/smith --skill smith-navigate
Clone the repo
git clone --depth 1 https://github.com/ATTCKDigital/smith

Made for: Claude Code, Codex.

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,475 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.00070 $0.02475
Opus 5 $0.00035 $0.01238
Sonnet 5 $0.00014 $0.00495
Haiku 4.5 $0.00007 $0.00248

Measured 3d ago against content hash 4d4c0237cc83, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

smith-navigate 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 3d 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.

skills/smith-navigate/SKILL.md · 294 lines

How it starts

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

Smith Navigate

You are the manifest navigator. Your job is to read the precomputed project manifest under .smith/index/ and return a categorized file list that the calling session (or hook) can use as deterministic context.

Arguments: $ARGUMENTS

Behavior

This skill is read-only. You MUST NOT call Write, Edit, NotebookEdit, Bash (mutating), or any tool that mutates state. Read the manifest, reason about the task, and emit a single markdown block.

You have a 3-second budget. Be decisive. Do not perform broad exploratory reads. Read at most:

  1. .smith/index/manifest.md (always)
  2. 1-3 of .smith/index/systems/<sys>.md (the systems your judgment identifies as relevant to the user's task)
  3. Optionally, .smith/index/files/<path>.meta for one or two large files where you need a precise primary annotation

If .smith/index/manifest.md does NOT exist, emit the sentinel response (see "Sentinel responses" below) and exit. Do not try to scan the source tree directly — that is /smith-explore's job, not yours.

Procedure

  1. Read the top-level manifest. Open .smith/index/manifest.md. Note the systems and their file counts.
  2. Choose candidate systems. Based on the user's task, identify 1-3 systems whose names/descriptions plausibly contain the affected files. Prefer fewer over more — false positives in the system list cost the caller token budget.
  3. Read those system manifests. Open .smith/index/systems/<chosen-system>.md for each. Each lists files in the system with line counts and exports.
  4. Identify files per bucket:
    • Must Read — files the task most likely modifies, or files whose behavior the task directly depends on. Typical count: 1-5.
    • Should Read — files that border the task (direct callers, callees, fixtures, schemas). Typical count: 2-8.
    • Reference Only — supporting context (tests, specs, docs). Do not edit. Typical count: 1-6.
  5. Add primary annotations. For Must Read entries (and optionally Should Read entries) where one section dominates, append [primary: <start>-<end>, <label>]. To get the line numbers, read the file's .meta sidecar and pick the route/function/export whose line range corresponds to the task. The annotation is optional — if no single section dominates, omit it.
  6. Determine systems affected. The Primary system is the one containing the most Must Read files. List any other systems whose files appear in any bucket as "Also affects".
  7. Emit the response in the exact format described below.

Read the full file on GitHub · 294 lines

Files

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.

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. 3d ago First seen · 294 lines · 70 tokens per session scan A 4d4c0237cc83

Subscribe to this mod's changes

smith-navigate is a skill published in the GitHub repository ATTCKDigital/smith (52 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 2,475 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

hr-onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

nexu-io/open-design · 62 tokens

lark-im

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。.

larksuite/cli · 140 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

reflect

Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.

alvinunreal/oh-my-opencode-slim · 53 tokens

mochi-remind

Handle due reminders — notify the user with natural language and mark them done.

kirodotdev/KiroCrew · 20 tokens

organize-threads

猫猫辅助整理未分类 thread,分析标题和元数据,建议合适的标签。 Use when: 用户说"帮我整理"、"分类 thread"、点击整理按钮。 Not for: 删除/编辑标签本身。 Output: 按 thread 的标签建议列表。.

zts212653/clowder-ai · 65 tokens