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.
npx agentmods add commands/signalcompose/claude-tools/trufflehog-scangit clone --depth 1 https://github.com/signalcompose/claude-toolsWrote 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.
[](https://agentmods.dev/commands/signalcompose/claude-tools/trufflehog-scan)<a href="https://agentmods.dev/commands/signalcompose/claude-tools/trufflehog-scan"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/trufflehog-scan.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00006 | $0.00795 |
| Opus 5 | $0.00003 | $0.00398 |
| Sonnet 5 | $0.00001 | $0.00159 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
trufflehog-scan 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TruffleHog Security Scan
Run TruffleHog security scan on the current project to detect exposed secrets.
Overview
This command:
- Checks TruffleHog installation
- Scans the current project's Git history
- Displays detected issues in detail
Execution Steps
STEP 1: Check TruffleHog Installation
which trufflehog
If not installed:
TruffleHog is not installed.
Install with:
brew install trufflehog
Run this command again after installation.
-> Abort
STEP 2: Verify Git Repository
pwd
git rev-parse --show-toplevel
If not a Git repository:
Current directory is not a Git repository.
TruffleHog can only scan Git repositories.
-> Abort
STEP 3: Execute TruffleHog Scan
trufflehog git file://. --json --no-update 2>/dev/null
Options:
git file://.: Scan current directory--json: JSON output format--no-update: Disable auto-update check
Timeout: 60 seconds (adjust for large repos)
STEP 4: Display Results
4-1. Summary
## TruffleHog Security Scan Results
**Project**: <project-name>
**Path**: <path>
**Branch**: <branch>
**Scan Date**: <date>
**Results**:
- Issues detected: N
4-2. Issues Detected
---
## Issues Detected
### Issue #1
- **File**: src/config/database.ts
- **Line**: 42
- **Type**: Generic API Key
- **Pattern**: AIza[0-9A-Za-z-_]{35}
- **Commit**: abc123def
- **Commit Date**: 2025-10-15 14:30
- **Recommended Actions**:
- Revoke this API key
- Move to environment variables
- Remove from history with git-filter-repo
### Issue #2
...
---
4-3. No Issues
## No Security Issues Detected
This project is clean.
No secret patterns were found.
STEP 5: Suggest Next Actions
## Recommended Actions
### If issues detected
1. Review each detection
2. Determine if false positive
3. For real secrets:
- Revoke/rotate the secret
- Move to environment variables
- Clean Git history (git-filter-repo)
### Cleaning Git History
```bash
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.
- 6d ago First seen · 173 lines · 6 tokens per session scan A 1bc3e80f4ef2
trufflehog-scan is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 9d ago), licensed MIT. It adds 6 tokens to every session and 795 once invoked, about $0.0000 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.
Other commands, from other repositories
commit
智能生成 Git 提交信息并提交.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
Command "release-plan" from alisunstar/OpenSunstar, covering /rd:release-plan — 发布计划, 先读, 执行, 产物 and 人工确认.