Scan a repository for secrets, keep an auditable baseline, and review only newly introduced findings during commits or CI checks.
Scanned 6/8/2026
Install via CLI
openskills install agentskillexchange/skills---
name: "Baseline and Review Repository Secret Findings with detect-secrets"
slug: "baseline-and-review-repository-secret-findings-with-detect-secrets"
description: "Scan a repository for secrets, keep an auditable baseline, and review only newly introduced findings during commits or CI checks."
github_stars: 4482
verification: "security_reviewed"
source: "https://github.com/Yelp/detect-secrets"
author: "Yelp"
publisher_type: "organization"
category: "Security & Verification"
framework: "Multi-Framework"
tool_ecosystem:
github_repo: "Yelp/detect-secrets"
github_stars: 4482
---
# Baseline and Review Repository Secret Findings with detect-secrets
Scan a repository for secrets, keep an auditable baseline, and review only newly introduced findings during commits or CI checks.
## Prerequisites
Python, detect-secrets CLI, git repository
## Installation
Use the upstream install or setup path that matches your environment:
- $ pip install detect-secrets
- $ brew install detect-secrets
- $ pip install detect-secrets[word_list]
- $ pip install detect-secrets[gibberish]
Requirements and caveats from upstream:
- python
- Specify path to custom filter. May be a python module
- is great for non-structured secrets, but may require tuning to adjust the scanning precision.
Basic usage or getting-started notes:
- Create a baseline of potential secrets currently found in your git repository.
- bash
- $ detect-secrets scan > .secrets.baseline
- Source: https://github.com/Yelp/detect-secrets
- Extracted from upstream docs: https://raw.githubusercontent.com/Yelp/detect-secrets/HEAD/README.md
## Documentation
- https://github.com/Yelp/detect-secrets
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/baseline-and-review-repository-secret-findings-with-detect-secrets/)
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.