Bibi
JimmyLv/BibiGPT-v1
BibiGPT CLI for summarizing videos, audio, and podcasts directly in the terminal.
Review AI API key leakage patterns and redaction strategies.
No licenceAuto-check: notes
Install Security AI Keys
$ npx skills add IgorWarzocha/Opencode-Workflows --skill security-ai-keys -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install IgorWarzocha/Opencode-Workflows security-ai-keys --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agents/security-reviewer/.opencode/skill/security-ai-keys .claude/skills/security-ai-keys && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "security-ai-keys" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/security-reviewer/.opencode/skill/security-ai-keys into .claude/skills/security-ai-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-ai-keys", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/security-reviewer/.opencode/skill/security-ai-keysType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add IgorWarzocha/Opencode-Workflows --skill security-ai-keys -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install IgorWarzocha/Opencode-Workflows security-ai-keys --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agents/security-reviewer/.opencode/skill/security-ai-keys .agents/skills/security-ai-keys && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "security-ai-keys" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/security-reviewer/.opencode/skill/security-ai-keys into .agents/skills/security-ai-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-ai-keys", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add IgorWarzocha/Opencode-Workflows --skill security-ai-keys -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install IgorWarzocha/Opencode-Workflows security-ai-keys --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agents/security-reviewer/.opencode/skill/security-ai-keys .cursor/skills/security-ai-keys && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "security-ai-keys" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/security-reviewer/.opencode/skill/security-ai-keys into .cursor/skills/security-ai-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-ai-keys", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/IgorWarzocha/Opencode-Workflows.git --path agents/security-reviewer/.opencode/skill/security-ai-keys--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add IgorWarzocha/Opencode-Workflows --skill security-ai-keys -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install IgorWarzocha/Opencode-Workflows security-ai-keys --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agents/security-reviewer/.opencode/skill/security-ai-keys .gemini/skills/security-ai-keys && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "security-ai-keys" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/security-reviewer/.opencode/skill/security-ai-keys into .gemini/skills/security-ai-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-ai-keys", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install IgorWarzocha/Opencode-Workflows security-ai-keysInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add IgorWarzocha/Opencode-Workflows --skill security-ai-keys -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .github/skills && cp -r skills-src/agents/security-reviewer/.opencode/skill/security-ai-keys .github/skills/security-ai-keys && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "security-ai-keys" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/security-reviewer/.opencode/skill/security-ai-keys into .github/skills/security-ai-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-ai-keys", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add IgorWarzocha/Opencode-Workflows --skill security-ai-keys -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install IgorWarzocha/Opencode-Workflows security-ai-keys --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgorWarzocha/Opencode-Workflows.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agents/security-reviewer/.opencode/skill/security-ai-keys .opencode/skills/security-ai-keys && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "security-ai-keys" agent skill from https://github.com/IgorWarzocha/Opencode-Workflows/tree/master/agents/security-reviewer/.opencode/skill/security-ai-keys into .opencode/skills/security-ai-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-ai-keys", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
security-ai-keys- GitHub stars
- 122
- Token cost
- ~793 tokens
- SKILL.md length
- 169 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- None found
At a glance
Review AI API key leakage patterns and redaction strategies.
- Works in 3 steps: Client-Side Exposure → Build Artifacts → Logs and Telemetry
- Identifying exposed keys for OpenAI
- SKILL.md covers Core Principles, Common Leak Paths, Quick Audit Commands and Hardening Checklist, plus 1 more section
- Runs Shell scripts from its folder; calls rg, gemini and aws; needs GOOGLE_APPLICATION_CREDENTIALS and AWS_ACCESS_KEY_ID
What it does
Security AI Keys is an agent skill from IgorWarzocha/Opencode-Workflows. Review AI API key leakage patterns and redaction strategies. Use for identifying exposed keys for OpenAI, Anthropic, Gemini, and 10+ other providers. Use proactively when code integrates AI providers or when environment variables/keys are present. Examples: - user: "Check for leaked OpenAI keys" → scan for sk- patterns and client-side exposure - user: "Is my Gemini integration secure?" → audit vertex AI config and key redaction - user: "Review AI provider logging" → ensure secrets are redacted from logs - user…
Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/scan.sh`).
It works with OpenAI and Vertex AI. The repository describes itself as: An ever evolving repository of Opencode workflow examples that might enhance your experience with it. I only left the stuff that actually works. YMMV.
When your agent uses it
- Identifying exposed keys for OpenAI
- 10+ other providers
Example prompts
- “Check for leaked OpenAI keys”
- “Is my Gemini integration secure?”
- “Review AI provider logging”
- “/security-ai-keys”
Requirements
- A Bash shell
- A credential in AWS_SECRET_ACCESS_KEY
- A credential in AZURE_OPENAI_API_KEY
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Client-Side Exposure
- Build Artifacts
- Logs and Telemetry
What it can do on your machine
Read from SKILL.md and the folder at commit 6444ec4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
rggeminiaws
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use aws, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
GOOGLE_APPLICATION_CREDENTIALSAWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAZURE_OPENAI_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Security AI Keys loads about 793 tokens when it runs. Until then it costs about 175 tokens; SKILL.md has 169 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:73
- [ ] `.env.local` and `.env.*.local` are gitignored
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 169 words (~793 tokens).
“Security audit patterns for AI API key leakage in applications integrating AI providers.”
- name
- security-ai-keys
Files
SKILL.md and 1 other file (scripts) in agents/security-reviewer/.opencode/skill/security-ai-keys of IgorWarzocha/Opencode-Workflows.
- SKILL.md
- scripts/scan.sh
Open the folder on GitHubat commit 6444ec4
Compare with similar skills
Security AI Keys next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Security AI Keys this skillIgorWarzocha/Opencode-Workflows | 122 | — | ~793 | Automated safety check: Notes | None | |
| BibiJimmyLv/BibiGPT-v1 | 6.2k | — | ~885 | Automated safety check: Pass | GPL-3.0 | |
| Kiln Check Finetune DeprecationKiln-AI/Kiln | 5.2k | — | ~1.9k | Automated safety check: Notes | Custom licence | |
| Telemetry AnalyticsOpenHands/OpenHands | 90k | — | ~305 | Automated safety check: Pass | MIT | |
| Add Model Pricelitefuse/litefuse | 100 | — | ~3.6k | Automated safety check: Pass | Custom licence | |
| Deploymentmatrixorigin/memoria | 609 | — | ~1.6k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Kiln Check Finetune Deprecation
Kiln-AI/Kiln
Check Kiln's fine-tunable model list for deprecated or unsupported base models.
Telemetry Analytics
OpenHands/OpenHands
This skill should be used when the user asks to "add tracking", "add a PostHog event", "change telemetry consent", "instrument onboarding", "debug analytics", or changes telemetry.ts…
Add Model Price
litefuse/litefuse
Add new LLM model pricing entries to Litefuse's default-model-prices.json.
Deployment
matrixorigin/memoria
Deploy Memoria with Docker Compose or Kubernetes. An agent skill from matrixorigin/memoria.
Letta Configuration
letta-ai/skills
Configure LLM models and providers for Letta agents and servers.
More from IgorWarzocha/Opencode-Workflows
All 35 skills in this repoCreate Opencode Plugin
IgorWarzocha/Opencode-Workflows
Create OpenCode plugins using the @opencode-ai/plugin SDK. An agent skill from IgorWarzocha/Opencode-Workflows.
Plugin Installer
IgorWarzocha/Opencode-Workflows
Find, install, and configure OpenCode plugins from the catalog or community.
Skill Creator
IgorWarzocha/Opencode-Workflows
Guide for creating effective opencode skills. An agent skill from IgorWarzocha/Opencode-Workflows.
Security Convex
IgorWarzocha/Opencode-Workflows
Review Convex security audit patterns for authentication and authorization.
Security Django
IgorWarzocha/Opencode-Workflows
Review Django security audit patterns for settings and middleware.
Security Docker
IgorWarzocha/Opencode-Workflows
Review Docker and container security audit patterns. An agent skill from IgorWarzocha/Opencode-Workflows.
Related
Questions about Security AI Keys
What does Security AI Keys do?
Review AI API key leakage patterns and redaction strategies. Security AI Keys is an agent skill from IgorWarzocha/Opencode-Workflows. Review AI API key leakage patterns and redaction strategies.
When should I use Security AI Keys?
Security AI Keys fits situations like: identifying exposed keys for OpenAI; 10+ other providers.
How do I install Security AI Keys in Claude Code?
Run `npx skills add IgorWarzocha/Opencode-Workflows --skill security-ai-keys -a claude-code`. Or copy the skill folder (agents/security-reviewer/.opencode/skill/security-ai-keys in IgorWarzocha/Opencode-Workflows) into .claude/skills/security-ai-keys in your project. Claude Code loads it when a task matches its description.
How do I install Security AI Keys in Codex?
Run `npx skills add IgorWarzocha/Opencode-Workflows --skill security-ai-keys -a codex`. Or copy the skill folder (agents/security-reviewer/.opencode/skill/security-ai-keys in IgorWarzocha/Opencode-Workflows) into .agents/skills/security-ai-keys in your project. Codex loads it when a task matches its description.
Can I use Security AI Keys in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add IgorWarzocha/Opencode-Workflows --skill security-ai-keys -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/security-ai-keys, .gemini/skills/security-ai-keys, .github/skills/security-ai-keys and .opencode/skills/security-ai-keys in your project.
What does Security AI Keys need to run?
Going by SKILL.md and its folder, Security AI Keys needs a shell for the scripts in its folder, the command-line tools its instructions call (rg, gemini and aws) and credentials named GOOGLE_APPLICATION_CREDENTIALS, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AZURE_OPENAI_API_KEY. Our summary lists: A Bash shell; A credential in AWS_SECRET_ACCESS_KEY; A credential in AZURE_OPENAI_API_KEY.
Does Security AI Keys access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Security AI Keys safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Security AI Keys use?
No licence was found for Security AI Keys or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Security AI Keys use?
About 793 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Security AI Keys?
Skills that share tags, products or a category with Security AI Keys: Bibi (JimmyLv/BibiGPT-v1, 6.2k stars), Kiln Check Finetune Deprecation (Kiln-AI/Kiln, 5.2k stars), Telemetry Analytics (OpenHands/OpenHands, 90k stars) and Add Model Price (litefuse/litefuse, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Security AI Keys?
IgorWarzocha (a GitHub user) maintains it in IgorWarzocha/Opencode-Workflows, which has 122 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on February 4, 2026.
Source: IgorWarzocha/Opencode-Workflows on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.