hf.scan-secrets-before-commit

hf.scan-secrets-before-commit is a skill for Claude Code, Codex from T-rav/hydraflow. It costs 15 tokens per session (754 once invoked), scanned A, original, Apache-2.0.

A pre-commit hook that checks added lines in staged Git files for patterns resembling API keys, tokens, or passwords before allowing `git commit` to proceed.

In plain words
What is it for?
Use it to scan staged changes whenever a Git commit command is about to run and block the commit when matching secret patterns are found.
Why use it?
It reduces the chance of committing credentials to the repository.

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/t-rav/hydraflow/hf.scan-secrets-before-commit
Any agent
npx skills add T-rav/hydraflow --skill hf.scan-secrets-before-commit
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.scan-secrets-before-commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/t-rav/hydraflow/hf.scan-secrets-before-commit.svg)](https://agentmods.dev/skills/t-rav/hydraflow/hf.scan-secrets-before-commit)
Your own site
<a href="https://agentmods.dev/skills/t-rav/hydraflow/hf.scan-secrets-before-commit"><img src="https://agentmods.dev/badge/skills/t-rav/hydraflow/hf.scan-secrets-before-commit.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 754 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.00015 $0.00754
Opus 5 $0.00008 $0.00377
Sonnet 5 $0.00003 $0.00151
Haiku 4.5 $0.00002 $0.00075

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

Security

Grade A, and why

hf.scan-secrets-before-commit 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.

.codex/skills/hf.scan-secrets-before-commit/SKILL.md · 78 lines

What it actually says

hf.scan-secrets-before-commit

#!/bin/bash
# Hook: Scan staged files for potential secrets before allowing commit.
# Fires on PreToolUse for Bash commands matching git commit.
# Blocks commit if API keys, tokens, or hardcoded passwords are found in staged diffs.

set -euo pipefail

INPUT=$(cat)
COMMAND=$(echo "$INPUT" | jq -r '.tool_input.command // empty')
CWD=$(echo "$INPUT" | jq -r '.cwd // empty')

# Only intercept git commit commands
if ! echo "$COMMAND" | grep -qE '(^|\s|&&\s*|;\s*)git commit'; then
  exit 0
fi

cd "$CWD"

# Get staged files
STAGED_FILES=$(git diff --cached --name-only 2>/dev/null || true)

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

# Get only the added lines from the staged diff (ignore removed lines)
ADDED_LINES=$(git diff --cached -U0 2>/dev/null | grep -E '^\+[^+]' || true)

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

# Define secret patterns (high-confidence, low false-positive)
PATTERNS=(
  'xoxb-[0-9]'                          # Slack bot tokens
  'xapp-[0-9]'                          # Slack app tokens
  'xoxp-[0-9]'                          # Slack user tokens
  'sk-[a-zA-Z0-9]{20,}'                 # OpenAI / Stripe keys
  'AKIA[0-9A-Z]{16}'                    # AWS access key IDs
  'ghp_[a-zA-Z0-9]{36}'                 # GitHub personal access tokens
  'ghs_[a-zA-Z0-9]{36}'                 # GitHub server tokens
  'glpat-[a-zA-Z0-9\-]{20}'             # GitLab personal access tokens
  'AIza[0-9A-Za-z\-_]{35}'              # Google API keys
)

# Build combined regex
COMBINED_PATTERN=$(printf '%s|' "${PATTERNS[@]}")
COMBINED_PATTERN="${COMBINED_PATTERN%|}"  # Remove trailing pipe

# Scan added lines for secrets
MATCHES=$(echo "$ADDED_LINES" | grep -oEn "$COMBINED_PATTERN" 2>/dev/null || true)

if [ -n "$MATCHES" ]; then
  echo "BLOCKED: Potential secrets detected in staged changes:" >&2
  echo "" >&2
  # Show which files contain the matches
  while IFS= read -r file; do
    [ -f "$file" ] || continue
    FILE_DIFF=$(git diff --cached -U0 -- "$file" 2>/dev/null | grep -E '^\+[^+]' || true)
    if echo "$FILE_DIFF" | grep -qE "$COMBINED_PATTERN" 2>/dev/null; then
      echo "  - $file" >&2
    fi
  done <<< "$STAGED_FILES"
  echo "" >&2
  echo "Remove secrets and use environment variables instead." >&2
  echo "If this is a false positive (e.g., test fixtures), ask the user to confirm." >&2
  exit 2
fi
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 · 78 lines · 15 tokens per session scan A df9ab39009be

Subscribe to this mod's changes

hf.scan-secrets-before-commit is a skill published in the GitHub repository T-rav/hydraflow (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 15 tokens to every session and 754 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 skills, from other repositories

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

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

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