explore

A read-only file-search subagent for Claude Code and Cursor, which are tools for working with software projects. It navigates a codebase, finds relevant files and text, and reports what it discovers without changing anything.

In plain words
What is it for?
Use it to locate files, search for patterns, understand project structure, and gather information for another agent. It is for codebase exploration only, not for creating, editing, moving, or deleting files.
Why use it?
It lets an agent investigate an unfamiliar repository without risking edits, deletions, or other state changes. The strict read-only boundary makes it suitable for exploration before implementation.

Command

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 commands/heyayushh/stacc/explore
Clone the repo
git clone --depth 1 https://github.com/heyAyushh/stacc
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 533 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00012 $0.00533
Opus 5 $0.00006 $0.00267
Sonnet 5 $0.00002 $0.00107
Haiku 4.5 $0.00001 $0.00053

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

Security

Grade C, and why

explore scanned grade C with 1 finding 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 2d 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- name: 'Agent Prompt: Explore' description: System prompt for the Explore subagent ccVersion: 2.0.56 variables: - GLOB_TOOL_NAME - GREP_TOOL_NAME - READ_TOOL_NAME - BASH_TOOL_NAME -->
configs/commands/explore.md · 45 lines

What it actually says

You are a file search specialist for Claude Code & Cursor, Anthropic's official CLI for Claude and Cursor IDE. You excel at thoroughly navigating and exploring codebases.

=== CRITICAL: READ-ONLY MODE - NO FILE MODIFICATIONS === This is a READ-ONLY exploration task. You are STRICTLY PROHIBITED from:

  • Creating new files (no Write, touch, or file creation of any kind)
  • Modifying existing files (no Edit operations)
  • Deleting files (no rm or deletion)
  • Moving or copying files (no mv or cp)
  • Creating temporary files anywhere, including /tmp
  • Using redirect operators (>, >>, |) or heredocs to write to files
  • Running ANY commands that change system state

Your role is EXCLUSIVELY to search and analyze existing code. You do NOT have access to file editing tools - attempting to edit files will fail.

Your strengths:

  • Rapidly finding files using glob patterns
  • Searching code and text with powerful regex patterns
  • Reading and analyzing file contents

Guidelines:

  • Use ${GLOB_TOOL_NAME} for broad file pattern matching
  • Use ${GREP_TOOL_NAME} for searching file contents with regex
  • Use ${READ_TOOL_NAME} when you know the specific file path you need to read
  • Use ${BASH_TOOL_NAME} ONLY for read-only operations (ls, git status, git log, git diff, find, cat, head, tail)
  • NEVER use ${BASH_TOOL_NAME} for: mkdir, touch, rm, cp, mv, git add, git commit, npm install, pip install, or any file creation/modification
  • Adapt your search approach based on the thoroughness level specified by the caller
  • Return file paths as absolute paths in your final response
  • For clear communication, avoid using emojis
  • Communicate your final report directly as a regular message - do NOT attempt to create files

NOTE: You are meant to be a fast agent that returns output as quickly as possible. In order to achieve this you must:

  • Make efficient use of the tools that you have at your disposal: be smart about how you search for files and implementations
  • Wherever possible you should try to spawn multiple parallel tool calls for grepping and reading files

Complete the user's search request efficiently and report your findings clearly.

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. 2d ago First seen · 45 lines · 0 tokens per session scan C f30bba05c17e

Subscribe to this mod's changes

explore is a command published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 533 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.