Detect hardcoded secrets in staged files and git history before commits.
npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-git
Please help me install this Agent Skill. Skill: ftm-git Source: https://github.com/kkudumu/feed-the-machine/tree/main/ftm-git Command: npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-git
Secrets leakage via Git happens when API keys, tokens, or credentials are accidentally committed. This Skill enforces a hard safety gate that scans staged files, working tree, and git history to detect hardcoded secrets and blocks commit or push operations until remediation is completed, reducing blast radius and credential rotation needs.
Enable the ftm-git gate in your repository and let it automatically scan for secrets, block unsafe commits, and perform remediation.
High-intent search queries and answers about installing and using this skill.
Blocking secrets from Git requires a pre-commit hook that scans staged files and the working tree for hardcoded credentials, intercepting unsafe commit and push operations before secrets enter version control history.
Automatic remediation of hardcoded API keys involves extracting secrets from source files into a gitignored .env file and refactoring the code to read from environment variables. This process creates the .env infrastructure and updates .gitignore safely.
The secret scanning pre-commit hook works with existing Git repositories by scanning both the working tree and git history. It requires Node and Git installed, integrating directly into your current commit and push workflow as a safety gate.
The best way to scan git history for leaked environment variables is using an automated scanning tool that checks staged files and historical commits for hardcoded secrets. It blocks unsafe commits and logs an audit trail for credential rotation tracking.
Yes, source code can be automatically refactored to read from environment variables during secret remediation. The process extracts hardcoded values to a .env file and updates the source files to reference environment variables instead of plain text credentials.
A pre-commit hook provides a continuous safety net beyond manual scanning by automatically blocking secrets before they enter git history. It enforces a hard safety gate on every commit and push, reducing the blast radius and need for credential rotation.
mpauloskyBlock commits containing detected secrets and forbid reading live .env files.
galaxyprojectRoute Nextflow conversion tasks to the appropriate Galaxy sub-skill.
m31uk3Guide complex problem solving through Observe, Orient, Decide, and Act phases.
0xHoneyJarScan environment files, client code, and git history for secret leakage.
