secret-crusade

secret-crusade is a command for Claude Code from btachinardi/church. It costs 33 tokens per session (3,842 once invoked), scanned A, original, MIT.

A secret-scanning command that searches source files and Git history for exposed credentials such as API keys, tokens, passwords, connection strings, and private keys.

In plain words
What is it for?
Use it to scan the current directory or a chosen path, optionally include the entire Git history, and inspect CI/CD, Docker, environment, and ignore-file configurations.
Why use it?
It helps locate sensitive values that may have been committed to a repository or exposed through configuration. Optional deeper checks inspect dependencies, containers, binary metadata, and strings that look deliberately hidden.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the church plugin — 1 skill, 14 commands, 14 agents shipped together

Good fit Use it to scan the current directory or a chosen path, optionally include the entire Git history, and inspect CI/CD, Docker, environment, and ignore-file configurations.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/btachinardi/church/secret-crusade
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.

Clone the repo
git clone --depth 1 https://github.com/btachinardi/church

Made for: Claude Code.

Or install church, the plugin that ships this one along with the rest of its 1 skill, 14 commands, 14 agents.

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 secret-crusade

README.md
[![agentmods](https://agentmods.dev/badge/commands/btachinardi/church/secret-crusade/github.svg)](https://agentmods.dev/commands/btachinardi/church/secret-crusade)
Your own site
<a href="https://agentmods.dev/commands/btachinardi/church/secret-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/secret-crusade/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 secret-crusade

Your own site · 80×15
<a href="https://agentmods.dev/commands/btachinardi/church/secret-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/secret-crusade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,842 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00033 $0.03842
Opus 5 $0.00016 $0.01921
Sonnet 5 $0.00007 $0.00768
Haiku 4.5 $0.00003 $0.00384

Measured 11d ago against content hash fcbce29aa724, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

secret-crusade 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 11d 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.

commands/secret-crusade.md · 522 lines

How it starts

The opening of the file, as written. The whole thing — 522 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the Secret Crusade Commander — orchestrating a coordinated security sweep to detect and eliminate credential leaks across the entire codebase and git history.

MISSION BRIEF

Deploy multiple Secret Purist squads in parallel to scan for:

  • Hardcoded API keys, tokens, passwords
  • Leaked credentials in git history
  • Misconfigured .gitignore and .env.example files
  • Secrets in CI/CD configurations
  • Connection strings and private keys
  • Suspicious high-entropy strings

COMMAND FLAGS

[path]

Target directory to scan. Defaults to current working directory.

--history

Enable git history scanning. WARNING: This scans ENTIRE git history with git log -p. Expensive but critical.

--deep

Enable deep analysis:

  • Dependency audit for suspicious packages
  • Docker and docker-compose inspection
  • Binary file metadata checks
  • Entropy analysis for obfuscated secrets

DEPLOYMENT PHASES

PHASE 1: RECONNAISSANCE

Before deploying squads, gather intelligence:

# Verify git repository
git rev-parse --is-inside-work-tree

# Count tracked files
git ls-files | wc -l

# Identify key areas
ls -la | grep -E "(\.env|\.git|docker|\.github|\.gitlab)"

# Check .gitignore exists
cat .gitignore 2>/dev/null || echo "WARNING: No .gitignore found"

Output to user:

🎯 RECONNAISSANCE COMPLETE

Target: /absolute/path/to/repo
Tracked files: 1,247
Git history depth: 2,384 commits
Flags: --history --deep

Deploying squads...

PHASE 2: SQUAD DEPLOYMENT

Deploy 2-4 parallel Secret Purist squads based on:

  • Repo size: <500 files = 2 squads, 500-2000 = 3 squads, >2000 = 4 squads
  • Flags: --history adds History Squad, --deep adds Dependency Audit Squad

Squad 1: File Scanner Squad

Objective: Scan all tracked files for secret patterns

Scope:

  • Source code files (.ts, .js, .py, .java, .go, etc.)
  • Configuration files (.json, .yaml, .toml, .ini)
  • Shell scripts (.sh, .bash)
  • Environment file templates (.env.example, .env.sample)

Read the full file on GitHub · 522 lines

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. 11d ago First seen · 522 lines · 0 tokens per session scan A fcbce29aa724

Subscribe to this mod's changes

secret-crusade is a command published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 3,842 once invoked, about $0.0002 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-30.