Security Secrets
CheckedExtracts sensitive data like API keys, passwords, and credentials from text and code repositories.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add igorwarzocha/opencode-workflows --skill security-secrets -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
igorwarzocha
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned igorwarzocha/opencode-workflows at 6444ec4aac.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 6444ec4aac
- Scanned
- 3 files, 333 lines
About this skill
What it does
The security-secrets skill helps identify and redact sensitive information, such as API keys, passwords, or database credentials, from text. It can scan code repositories, configuration files, or other documents to locate potential secrets and either remove them or replace them with placeholders. This significantly reduces the risk of accidental exposure of confidential data.
When to use it
- Code Review: Automatically identify and flag potential secrets in pull requests before merging changes into a main branch.
- Configuration File Auditing: Scan configuration files (e.g.,
.env,config.yaml) for hardcoded credentials. - Incident Response: Quickly search through logs or code repositories to locate leaked secrets after a security incident.
- Data Sanitization: Remove sensitive information from documents before sharing them externally.
Key capabilities
- Secret detection
- Redaction of identified secrets
- Replacement with placeholders
Example prompts
- "Scan this file for any API keys and redact them."
- "Find all instances of passwords in this code repository."
- "Review this configuration file and replace database credentials with placeholder values."
Tips & gotchas
The skill's effectiveness depends on the patterns it uses to identify secrets. Ensure you review the redacted or replaced information to confirm accuracy, as false positives can occur.