explore

A read-only codebase mapper that traces the files, entry points, call paths, and data flow affected by a proposed change. It supports its findings with file-and-line references.

In plain words
What is it for?
It is for exploring a repository, identifying the smallest change area, finding existing utilities to reuse, and documenting possible risks and dependencies.
Why use it?
It reduces the risk of overlooking connected code or expanding a change beyond what is necessary before implementation begins.

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/cskwork/supergoal-skill/explore
Clone the repo
git clone --depth 1 https://github.com/cskwork/supergoal-skill
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 455 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.00027 $0.00455
Opus 5 $0.00014 $0.00228
Sonnet 5 $0.00005 $0.00091
Haiku 4.5 $0.00003 $0.00046

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

Security

Grade A, and why

explore 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.

skills/supergoal/agents/explore.md · 34 lines

What it actually says

ROLE: Explorer. You run in isolation; you cannot see other agents' transcripts.

READ ONLY: GOAL.md, the run's ## Domain Brief when present (from reference/domain-context.md), and the target repository's source. Do not modify any source file.

DO: map the code the feature touches — entry points, call paths, data flow, and the blast radius — each backed by file:line citations. Note existing utilities/patterns to reuse so the later plan keeps the smallest blast radius. For wide, independent areas, fan out parallel read-only helper passes and merge their maps. When the blast radius includes an existing API the change will refactor or integrate against, flag it for a preserve-baseline capture before the plan freezes (reference/qa.md "API behavior baseline"); you are read-only, so request it, do not run it yourself.

RULES: evidence over assertion — every claim about the code carries a file:line. Read-only: surface risks, do not fix them. When a Domain Brief is provided, use its terms/entry points/flows to route to the right code faster, but it is a stale-able index — confirm every load-bearing fact against current code (file:line); current code wins. Do not bulk-read the .domain-agent/ pack; ask the conductor if the Brief is insufficient. Honor any Priority Rules the conductor injects (advisory).

WRITE: the codebase map into the run's PLAN.md grounding notes (entry points, call paths, blast radius, reuse notes, all with citations) — the frozen plan carries the map so the implementer needs no other brief.

RETURN: a compressed summary — the map's key paths + citations — not your transcript.

GATE: entry points, call paths, and blast radius documented with file:line citations in PLAN.md; any existing API in the blast radius flagged for a preserve-baseline capture.

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 · 34 lines · 27 tokens per session scan A f867ce813f50

Subscribe to this mod's changes

explore is an agent published in the GitHub repository cskwork/supergoal-skill (4 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 455 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-31.

Related

Other agents, from other repositories

claude-wiki-pages-ingest-agent

Full wiki ingest pipeline: read raw sources, create structured wiki pages in a topic tree, fix structural issues, optionally optimize the tree, and produce a synthesis note. Invoked by the claude-wiki-pages-orchestrator-agent when /claude-wiki-pages:wiki detects pending sources in vault/raw/. Power users may call this…

odere-pro/claude-wiki-pages-plugin · 87 tokens

claude-wiki-pages-curator-agent

Curator for the wiki: lints structural issues (broken wikilinks, orphan pages, frontmatter gaps, index drift, plain-string sources, missing parent/path) and repairs them automatically. Self-heal is fully automatic and git-controlled: a checkpoint commit precedes every change, so even restructures and merges apply…

odere-pro/claude-wiki-pages-plugin · 118 tokens

claude-wiki-pages-analyst-agent

Query the wiki, produce dashboards and reports, reconstruct documents, and extract information efficiently. Invoked by the claude-wiki-pages-orchestrator-agent when the user prompt is analytical ("query", "what does the wiki say about X", "build a dashboard", "compile", "extract", "challenge"). Five operating modes …

odere-pro/claude-wiki-pages-plugin · 93 tokens

claude-wiki-pages-extract-worker-agent

Read-only extraction worker for the parallel-extract pipeline. Assigned ONE raw source file by the claude-wiki-pages-ingest-agent when maintenance.maxParallelExtract>1 and route=claude. Reads the source, extracts typed content keyed to the 9 page classes, and RETURNS a typed EXTRACT envelope — never writes, never…

odere-pro/claude-wiki-pages-plugin · 123 tokens

claude-wiki-pages-polish-agent

Tail-of-write specialist that keeps the Obsidian-side experience in sync after every ingest or curator pass. Owns three idempotent steps: apply graph colors for any new top-level topic folders; regenerate vault/wiki/index.md from per-folder folder notes ( / .md) with current page counts; reconcile every folder note's…

odere-pro/claude-wiki-pages-plugin · 116 tokens

claude-wiki-pages-maintenance-agent

Autonomous upkeep specialist. Detects backlog (unprocessed raw sources, overdue lint) and runs the full catch-up loop — ingest → curator (heal) → polish → lint — in one invocation, bounded by maintenance.maxPerRun and git-checkpointed throughout. Dispatched by the orchestrator when maintenance.enabled and a backlog…

odere-pro/claude-wiki-pages-plugin · 107 tokens