hydraflow: Skill for Claude Code

.codex/skills/hf.track-code-changes/SKILL.md

hf.track-code-changes is a skill for Claude Code, Codex from T-rav/hydraflow. It costs 11 tokens per session (304 once invoked), scanned B, original, Apache-2.0.

A file-change hook that records when tracked source files are edited during a session. A hook is an automated action triggered by another tool event.

In plain words
What is it for?
Use it after edit or write operations to track changes in Python, JavaScript, TypeScript, HTML, CSS, YAML, Markdown, and Dockerfiles.
Why use it?
It gives stop-session review hooks a reliable signal and ignores unrelated files such as configuration under `.claude/`.

Skill for Claude CodeCodex

Written for Claude Code and Codex: ${CLAUDE_PROJECT_DIR variable, but also installed under .codex/.

This is T-rav/hydraflow's own configuration. It tells Claude Code and Codex how to work on hydraflow itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hydraflow configures →

Reuse

Borrowing it

Nothing to install: this file belongs to T-rav/hydraflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/T-rav/hydraflow/staging/.codex/skills/hf.track-code-changes/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/T-rav/hydraflow

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for hf.track-code-changes

README.md
[![agentmods](https://agentmods.dev/badge/skills/t-rav/hydraflow/hf.track-code-changes/github.svg)](https://agentmods.dev/skills/t-rav/hydraflow/hf.track-code-changes)
Your own site
<a href="https://agentmods.dev/skills/t-rav/hydraflow/hf.track-code-changes"><img src="https://agentmods.dev/badge/skills/t-rav/hydraflow/hf.track-code-changes/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for hf.track-code-changes

Your own site · 80×15
<a href="https://agentmods.dev/skills/t-rav/hydraflow/hf.track-code-changes"><img src="https://agentmods.dev/badge/skills/t-rav/hydraflow/hf.track-code-changes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 304 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00011 $0.00304
Opus 5.5 $0.00004 $0.00122
Sonnet 5.5 $0.00002 $0.00061
Haiku 4.5 $0.00001 $0.00030

Measured 1mo ago against content hash ff3e1ee6f7f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

hf.track-code-changes scanned grade B 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 1mo 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

if echo "$FILE_PATH" | grep -qE '\.claude/'; then
.codex/skills/hf.track-code-changes/SKILL.md · 43 lines

What it actually says

hf.track-code-changes

#!/bin/bash
# Hook: Set a marker when source code is modified during a session.
# Fires on PostToolUse for Edit and Write.
# Stop agent hooks check this marker to skip review when no code changed.

set -euo pipefail

INPUT=$(cat)
FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty')

if [ -z "$FILE_PATH" ]; then
  exit 0
fi

# Only track source files
if ! echo "$FILE_PATH" | grep -qE '\.(py|ts|tsx|js|jsx|html|css|yml|yaml|md)$'; then
  # Also check for Dockerfiles
  if ! echo "$FILE_PATH" | grep -qiE 'Dockerfile'; then
    exit 0
  fi
fi

# Skip .claude/ config files — editing hooks/settings isn't "code"
if echo "$FILE_PATH" | grep -qE '\.claude/'; then
  exit 0
fi

PROJECT_DIR="${CLAUDE_PROJECT_DIR:-$(pwd)}"
MARKER_DIR="/tmp/claude-code-markers/$(echo -n "$PROJECT_DIR" | md5)"
mkdir -p "$MARKER_DIR"
touch "$MARKER_DIR/code-changed"

exit 0
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. 1mo ago First seen · 43 lines · 11 tokens per session scan B ff3e1ee6f7f2

Subscribe to this mod's changes

hf.track-code-changes is a skill published in the GitHub repository T-rav/hydraflow (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 11 tokens to every session and 304 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

develop

Run /develop to build a feature, UI or backend, from an approved design, a page, component, API, service, or data slice. If something load bearing is undecided and no spec records it, it stops and routes you to /architect; otherwise it reads the spec plus AGENTS.md, builds, and advances the scope.

jsmastery-pro/skills · 71 tokens

sync

Run /sync as the last step after a change is complete, around merge, to keep durable knowledge current. Updates root and nested AGENTS.md, reconciles the scope from repo evidence, and flags specs the change made stale. Surgical edits only: it adds lines, and rewrites single lines it owns. Never a whole section, never…

jsmastery-pro/skills · 73 tokens

document

Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.

jsmastery-pro/skills · 65 tokens

debug

Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test. No features, no extra refactors.

jsmastery-pro/skills · 74 tokens

check

Confirm a change before merge. /check verify drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). /check review runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never…

jsmastery-pro/skills · 74 tokens

architect

Run /architect when choosing between approaches, designing a feature or page, picking a tech stack, or when /develop says a decision is owed, anytime a load bearing technical decision is unmade. Asks deep questions, recommends an answer, and writes a build spec to docs/specs/. Owns all spec files.

jsmastery-pro/skills · 66 tokens