hf.track-exploration

Record per-session markers for Read and Grep exploration actions.

5|2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/T-rav/hydraflow --skill hf-track-exploration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf.track-exploration
Source: https://github.com/T-rav/hydraflow/tree/main/.codex/skills/hf.track-exploration
Command: npx skills add https://github.com/T-rav/hydraflow --skill hf-track-exploration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that any code exploration activity (Read/Grep) is recorded for audit and compliance, enabling verification that exploration occurred within a session.

Core Features & Use Cases

  • Tracks Read/Grep actions by emitting a per-session exploration marker.
  • Creates a lightweight, per-project marker that can be checked by an edit guard.
  • Supports auditing and traceability for development workflows.

Quick Start

Track code exploration during an active development session to generate the marker.

Frequently Asked Questions about hf.track-exploration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track code exploration activity during a development session?

Track code exploration by recording a per-session marker when Read or Grep actions occur. A PostToolUse hook creates a per-project marker in /tmp/claude-code-markers, exposing a persistent 'explored' flag for validation.

Can I audit whether code reading or searching was performed in a session?

Yes, audit code reading and searching by checking the per-project marker generated in /tmp/claude-code-markers. This marker verifies that exploration occurred within the active development session.

Does code exploration tracking work with Read and Grep tools across any project?

Code exploration tracking applies across any project where code reading or searching is performed. The PostToolUse hook intercepts Read and Grep actions to emit the session marker.

How do I validate that code exploration occurred before applying edits?

Validate exploration by checking the persistent 'explored' flag exposed by the tracking marker. The edit guard reads this flag to verify that Read or Grep actions occurred before allowing modifications.

What is a session marker for code navigation and when do I need it?

A session marker is a lightweight file in /tmp/claude-code-markers recording that code exploration happened. You need it for compliance auditing and to enforce traceability in development workflows.

Do I need to install dependencies to track code exploration events?

No dependencies are required to track code exploration events. The Skill operates standalone using a PostToolUse hook to generate markers and expose the 'explored' flag.