Iron Proxy Gateway for NanoClaw
nanocoai/nanoclaw
Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.
This skill should be used when the user asks to "find hardcoded secrets", "audit for credential leaks", "check for API keys in code", "review secret scanning alerts", "rotate a leaked secret", or…
Install Detecting Secrets
$ npx skills add bitwarden/ai-plugins --skill detecting-secrets -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bitwarden/ai-plugins detecting-secrets --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/bitwarden/ai-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/bitwarden-security-engineer/skills/detecting-secrets .claude/skills/detecting-secrets && 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 "detecting-secrets" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-security-engineer/skills/detecting-secrets into .claude/skills/detecting-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-secrets", 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/bitwarden/ai-plugins/tree/main/plugins/bitwarden-security-engineer/skills/detecting-secretsType 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 bitwarden/ai-plugins --skill detecting-secrets -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bitwarden/ai-plugins detecting-secrets --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/bitwarden-security-engineer/skills/detecting-secrets .agents/skills/detecting-secrets && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "detecting-secrets" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-security-engineer/skills/detecting-secrets into .agents/skills/detecting-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-secrets", 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 bitwarden/ai-plugins --skill detecting-secrets -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bitwarden/ai-plugins detecting-secrets --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/bitwarden-security-engineer/skills/detecting-secrets .cursor/skills/detecting-secrets && 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 "detecting-secrets" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-security-engineer/skills/detecting-secrets into .cursor/skills/detecting-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-secrets", 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/bitwarden/ai-plugins.git --path plugins/bitwarden-security-engineer/skills/detecting-secrets--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 bitwarden/ai-plugins --skill detecting-secrets -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bitwarden/ai-plugins detecting-secrets --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/bitwarden-security-engineer/skills/detecting-secrets .gemini/skills/detecting-secrets && 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 "detecting-secrets" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-security-engineer/skills/detecting-secrets into .gemini/skills/detecting-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-secrets", 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 bitwarden/ai-plugins detecting-secretsInstalls 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 bitwarden/ai-plugins --skill detecting-secrets -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/bitwarden-security-engineer/skills/detecting-secrets .github/skills/detecting-secrets && 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 "detecting-secrets" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-security-engineer/skills/detecting-secrets into .github/skills/detecting-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-secrets", 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 bitwarden/ai-plugins --skill detecting-secrets -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bitwarden/ai-plugins detecting-secrets --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/bitwarden-security-engineer/skills/detecting-secrets .opencode/skills/detecting-secrets && 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 "detecting-secrets" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-security-engineer/skills/detecting-secrets into .opencode/skills/detecting-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-secrets", 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
detecting-secrets- GitHub stars
- 154
- Token cost
- ~2.1k tokens
- SKILL.md length
- 661 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
This skill should be used when the user asks to "find hardcoded secrets", "audit for credential leaks", "check for API keys in code", "review secret scanning alerts", "rotate a leaked secret", or…
- Works in 4 steps: Rotate Immediately → Remove from Code → Remove from Git History (If Needed) → …
- Asks to find hardcoded secrets
- SKILL.md covers Secret Patterns, Context-Aware Detection, Common Hiding Spots and GitHub Secret Scanning…, plus 3 more sections
- Calls gh and git
What it does
Detecting Secrets is an agent skill from bitwarden/ai-plugins, published by the product's own GitHub organization. This skill should be used when the user asks to "find hardcoded secrets", "audit for credential leaks", "check for API keys in code", "review secret scanning alerts", "rotate a leaked secret", or needs to detect hardcoded credentials, review secret handling patterns, or remediate exposed secrets.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Secrets management. The repository describes itself as: AI plugin marketplace.
When your agent uses it
- Asks to find hardcoded secrets
- Audit for credential leaks
- Check for API keys in code
- Review secret scanning alerts
Example prompts
- “find hardcoded secrets”
- “audit for credential leaks”
- “check for API keys in code”
- “/detecting-secrets”
Requirements
- Docker
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Rotate Immediately
- Remove from Code
- Remove from Git History (If Needed)
- Prevent Recurrence
What it can do on your machine
Read from SKILL.md and the folder at commit 0047fdf. 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
Shell commands in SKILL.md call:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, 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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Detecting Secrets loads about 2.1k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 661 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:76
| `.env` / `.env.local` | Environment variable definitions with real values | - NoteMentions a .env fileSKILL.md:143
r files that should never be committed (`.env`, `*.pfx`, `appsettings.Development.json`) - NoteMentions a .env fileSKILL.md:159
local development, use user-secrets or `.env` files that are `.gitignore`d — never commit them.
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); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 661 words (~2,096 tokens).
“Look for these categories of hardcoded secrets in code:”
- name
- detecting-secrets
Files
Just SKILL.md in plugins/bitwarden-security-engineer/skills/detecting-secrets of bitwarden/ai-plugins.
Open the folder on GitHubat commit 0047fdf
Compare with similar skills
Detecting Secrets 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 |
|---|---|---|---|---|---|---|
| Detecting Secrets this skillbitwarden/ai-plugins | 154 | — | ~2.1k | Automated safety check: Notes | Custom licence | |
| Iron Proxy Gateway for NanoClawnanocoai/nanoclaw | 31k | — | ~4.6k | Automated safety check: Notes | MIT | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Env Var Conventionssgl-project/sglang | 37k | 2 repos | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Mac Fleet Maintenancesteipete/agent-scripts | 7.3k | — | ~4.8k | Automated safety check: Pass | MIT | |
| Add Config Env Varbaserow/baserow | 6.1k | — | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
Env Var Conventions
sgl-project/sglang
Conventions for SGLang environment variables — where to define, how to access, how to name, and how to deprecate.
Mac Fleet Maintenance
steipete/agent-scripts
Inventories and maintains a fleet of Macs from a desired-state file: package updates, repo and Xcode sync, and disk, backup and security health reports.
Add Config Env Var
baserow/baserow
Add a Baserow configuration environment variable for the backend, frontend, or both, and propagate it through settings, Nuxt runtime config, Docker Compose, documentation, consumers, and tests as…
Edgeone Makers CLI
TencentEdgeOne/edgeone-makers-tools
EdgeOne Makers CLI command reference. An agent skill from TencentEdgeOne/edgeone-makers-tools.
More from bitwarden/ai-plugins
All 33 skills in this repo- Official
Reviewing Claude Config
bitwarden/ai-plugins
Reviews Claude configuration files for security, structure, and prompt engineering quality.
- Official
Managing Workflow Secrets
bitwarden/ai-plugins
Bitwarden's canonical pattern for using a secret inside a GitHub Actions job: authenticate to Azure with the OIDC triad, pull the secret from an Azure Key Vault via the bitwarden/gh-actions…
- Official
Reviewing Security Architecture
bitwarden/ai-plugins
This skill should be used when the user asks to "review the security architecture", "check authentication patterns", "evaluate trust boundaries", "review encryption implementation", "assess…
- Official
Auditing External Claude Plugins
bitwarden/ai-plugins
Audits an external (third-party) Claude Code plugin pinned in this marketplace for security risk before it is vendored, and writes the report to a file for downstream posting.
- Official
Action Audit
bitwarden/ai-plugins
Audit GitHub Actions action usage across an org. An agent skill from bitwarden/ai-plugins.
- Official
Action Remediate
bitwarden/ai-plugins
Remediate GitHub Actions action findings identified by the action-audit skill.
Related
Categories
Questions about Detecting Secrets
What does Detecting Secrets do?
This skill should be used when the user asks to "find hardcoded secrets", "audit for credential leaks", "check for API keys in code", "review secret scanning alerts", "rotate a leaked secret", or…. Detecting Secrets is an agent skill from bitwarden/ai-plugins, published by the product's own GitHub organization. This skill should be used when the user asks to "find hardcoded secrets", "audit for credential leaks", "check for API keys in code", "review secret scanning alerts", "rotate a leaked secret", or needs to detect hardcoded credentials, review secret handling patterns, or remediate exposed secrets.
When should I use Detecting Secrets?
Detecting Secrets fits situations like: asks to find hardcoded secrets; audit for credential leaks; check for API keys in code; review secret scanning alerts.
How do I install Detecting Secrets in Claude Code?
Run `npx skills add bitwarden/ai-plugins --skill detecting-secrets -a claude-code`. Or copy the skill folder (plugins/bitwarden-security-engineer/skills/detecting-secrets in bitwarden/ai-plugins) into .claude/skills/detecting-secrets in your project. Claude Code loads it when a task matches its description.
How do I install Detecting Secrets in Codex?
Run `npx skills add bitwarden/ai-plugins --skill detecting-secrets -a codex`. Or copy the skill folder (plugins/bitwarden-security-engineer/skills/detecting-secrets in bitwarden/ai-plugins) into .agents/skills/detecting-secrets in your project. Codex loads it when a task matches its description.
Can I use Detecting Secrets 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 bitwarden/ai-plugins --skill detecting-secrets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/detecting-secrets, .gemini/skills/detecting-secrets, .github/skills/detecting-secrets and .opencode/skills/detecting-secrets in your project.
What does Detecting Secrets need to run?
Going by SKILL.md and its folder, Detecting Secrets needs the command-line tools its instructions call (gh and git). Our summary lists: Docker.
Does Detecting Secrets access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Detecting Secrets 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. Review the folder before installing.
What licence does Detecting Secrets use?
Detecting Secrets has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Detecting Secrets use?
About 2.1k tokens (SKILL.md is roughly 8.4k 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 Detecting Secrets?
Skills that share tags, products or a category with Detecting Secrets: Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Env Var Conventions (sgl-project/sglang, 37k stars) and Mac Fleet Maintenance (steipete/agent-scripts, 7.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Detecting Secrets?
bitwarden (a GitHub organization, an official publisher) maintains it in bitwarden/ai-plugins, which has 154 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 6, 2026.
Source: bitwarden/ai-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.