Security Secrets
IgorWarzocha/Opencode-Workflows
Review secret detection patterns and scanning workflows. An agent skill from IgorWarzocha/Opencode-Workflows.
Agent skill
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Scan a source-code tree for hardcoded credentials embedded in source files: AWS access keys, GitHub tokens, Stripe keys, Slack tokens, Anthropic API keys, OpenAI keys, JWT signing secrets, generic…
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill scanning-for-hardcoded-secrets -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace scanning-for-hardcoded-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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/scanning-for-hardcoded-secrets .claude/skills/scanning-for-hardcoded-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 "scanning-for-hardcoded-secrets" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/scanning-for-hardcoded-secrets into .claude/skills/scanning-for-hardcoded-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scanning-for-hardcoded-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/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/scanning-for-hardcoded-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 jeremylongshore/tons-of-skills-marketplace --skill scanning-for-hardcoded-secrets -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace scanning-for-hardcoded-secrets --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/scanning-for-hardcoded-secrets .agents/skills/scanning-for-hardcoded-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 "scanning-for-hardcoded-secrets" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/scanning-for-hardcoded-secrets into .agents/skills/scanning-for-hardcoded-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scanning-for-hardcoded-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 jeremylongshore/tons-of-skills-marketplace --skill scanning-for-hardcoded-secrets -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace scanning-for-hardcoded-secrets --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/scanning-for-hardcoded-secrets .cursor/skills/scanning-for-hardcoded-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 "scanning-for-hardcoded-secrets" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/scanning-for-hardcoded-secrets into .cursor/skills/scanning-for-hardcoded-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scanning-for-hardcoded-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/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/scanning-for-hardcoded-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 jeremylongshore/tons-of-skills-marketplace --skill scanning-for-hardcoded-secrets -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace scanning-for-hardcoded-secrets --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/scanning-for-hardcoded-secrets .gemini/skills/scanning-for-hardcoded-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 "scanning-for-hardcoded-secrets" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/scanning-for-hardcoded-secrets into .gemini/skills/scanning-for-hardcoded-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scanning-for-hardcoded-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 jeremylongshore/tons-of-skills-marketplace scanning-for-hardcoded-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 jeremylongshore/tons-of-skills-marketplace --skill scanning-for-hardcoded-secrets -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/scanning-for-hardcoded-secrets .github/skills/scanning-for-hardcoded-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 "scanning-for-hardcoded-secrets" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/scanning-for-hardcoded-secrets into .github/skills/scanning-for-hardcoded-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scanning-for-hardcoded-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 jeremylongshore/tons-of-skills-marketplace --skill scanning-for-hardcoded-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 jeremylongshore/tons-of-skills-marketplace scanning-for-hardcoded-secrets --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/scanning-for-hardcoded-secrets .opencode/skills/scanning-for-hardcoded-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 "scanning-for-hardcoded-secrets" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/scanning-for-hardcoded-secrets into .opencode/skills/scanning-for-hardcoded-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scanning-for-hardcoded-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.
scanning-for-hardcoded-secretsScan a source-code tree for hardcoded credentials embedded in source files: AWS access keys, GitHub tokens, Stripe keys, Slack tokens, Anthropic API keys, OpenAI keys, JWT signing secrets, generic…
Scanning For Hardcoded Secrets is an agent skill from jeremylongshore/tons-of-skills-marketplace. Scan a source-code tree for hardcoded credentials embedded in source files: AWS access keys, GitHub tokens, Stripe keys, Slack tokens, Anthropic API keys, OpenAI keys, JWT signing secrets, generic base64-encoded passwords, RSA / SSH private keys, and high-entropy string literals that pattern-match common credential shapes. Use when: pre-commit gate before pushing a feature branch, audit before SOC2, post-incident scan after a leak, or inheriting a codebase you didn't write. Threshold: any source file contains a…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/PLAYBOOK.md`, `references/THEORY.md` and `scripts/scan_secrets.py`). Compatibility notes: Designed for Claude Code
It sits in DevOps & Cloud, covering Secrets management, Authentication and SOC 2 and security compliance. It works with Amazon Web Services, GitHub, Slack and Stripe. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBash(python3:*)GlobGrepFrom allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3gitjqFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
JWT_SECRETFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Scanning For Hardcoded Secrets loads about 2.1k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 203 tokens; SKILL.md has 707 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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- Write(.env)- Edit(.env)| `.env`-shaped KEY=VALUE in non-`.env` file | **HIGH** | Multiple `[A-Z_]+=` lines in `.py`/`.js`/`.md` files | CWE-200(Python dotenv, Node .env+dotenv, Ruby Rails credentials, GoAutomated 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.
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 707 words, ~2,115 tokens.
.claude/skills/scanning-for-hardcoded-secrets/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.The single most common cause of credential breach in 2026 remains
hardcoded secrets in source code. Engineers paste an API key into a
config file "just for testing," forget to remove it, commit the
file. The credential is now in the repository's history forever
(git rebase doesn't help if anyone cloned in between) and
extractable by anyone who reaches the repo: contractors,
ex-employees, attackers via .git/ directory exposure (see skill
six), GitHub bot scrapers crawling public repos.
The cost of detection-after-commit is near-zero (free tools exist: gitleaks, trufflehog, this skill). The cost of detection-before-commit is also near-zero (pre-commit hooks). The cost of remediation after the fact is rotating every credential exposed + auditing for exploitation + potentially notifying customers of breach. The asymmetry is severe, the discipline is the only constraint.
This skill scans a filesystem tree, matching against a canonical regex library covering the credential shapes attackers and bots search for first.
| Finding | Severity | Threshold | Affected control |
|---|---|---|---|
| AWS access key (AKIA-prefix) | CRITICAL | Literal AKIA[0-9A-Z]{16} in any file | CWE-798 |
| AWS secret access key | CRITICAL | 40-char base64 in aws_secret_access_key field context | CWE-798 |
| GitHub personal access token | CRITICAL | ghp_[A-Za-z0-9]{36} or gho_, ghu_, ghs_, ghr_ | CWE-798 |
| GitHub app installation token | CRITICAL | ghs_[A-Za-z0-9]{36} | CWE-798 |
| Stripe live key | CRITICAL | sk_live_[A-Za-z0-9]{24,} | CWE-798 |
| Stripe test key | MEDIUM | sk_test_[A-Za-z0-9]{24,} | CWE-798 |
| Anthropic API key | CRITICAL | sk-ant-api03-[A-Za-z0-9_-]{93} or similar | CWE-798 |
| OpenAI API key | CRITICAL | sk-(proj-)?[A-Za-z0-9_-]{40,} | CWE-798 |
| Slack bot token | CRITICAL | xoxb-[A-Za-z0-9-]+ | CWE-798 |
| Slack user token | CRITICAL | xoxp-[A-Za-z0-9-]+ | CWE-798 |
| Google API key | HIGH | AIza[A-Za-z0-9_-]{35} | CWE-798 |
| RSA / OpenSSH private key | CRITICAL | BEGIN PRIVATE KEY header (RSA, OPENSSH, EC, DSA variants) | CWE-321 |
| JWT secret | HIGH | Long string in jwt_secret, JWT_SECRET, signing_secret field | CWE-321 |
| Generic password literal | HIGH | password = "..." with non-placeholder value | CWE-798 |
| High-entropy string in key/token field | MEDIUM | Shannon entropy ≥ 4.5 in key:/token: field context | CWE-798 |
.env-shaped KEY=VALUE in non-.env file | HIGH | Multiple [A-Z_]+= lines in .py/.js/.md files | CWE-200 |
This skill scans a filesystem path. No authorization gate (it operates on local source code, not network targets).
python3 ${CLAUDE_PLUGIN_ROOT}/skills/scanning-for-hardcoded-secrets/scripts/scan_secrets.py /path/to/repoOptions:
Usage: scan_secrets.py PATH [OPTIONS]
Options:
--output FILE Write findings to FILE (default: stdout)
--format FMT json | jsonl | markdown (default: markdown)
--min-severity SEV (default: info)
--include-tests Include files under tests/, test/, __tests__/, spec/
(default: excluded to reduce false positives)
--git-history N Also scan the last N git commits' diffs (default: 0
= working tree only)
--exclude GLOB Skip files matching glob (repeatable)
--entropy-only Only flag entropy-based findings (skip regex)The scanner walks the tree, applies the regex library to every file's contents, and emits a Finding per match with file path, line number, severity, and the redacted matched text.
CRITICAL = the matched string is a real credential shape that upstream tools auto-extract. Rotate the credential immediately. Audit logs for any API call against that credential since the commit landed.
HIGH = pattern strongly suggests credential but requires manual verification (the literal might be a placeholder or test fixture).
MEDIUM / LOW = entropy-based heuristic that needs human review.
For any confirmed real credential:
references/PLAYBOOK.md for per-language patterns.git filter-repo or BFG Repo-Cleaner can purge the secret from history, but only if you
can force-push and coordinate with every clone-holder. For
public repos, history-scrub is often not worth the disruption
compared to just rotating.# .git/hooks/pre-commit (or via pre-commit framework)
python3 plugins/security/penetration-tester/skills/scanning-for-hardcoded-secrets/scripts/scan_secrets.py \
--min-severity high --format json . | jq -e 'length == 0' \
|| { echo "Secrets detected. Fix before commit."; exit 1; }- name: Hardcoded-secrets scan
run: |
python3 plugins/security/penetration-tester/skills/scanning-for-hardcoded-secrets/scripts/scan_secrets.py \
. --min-severity high --format json --output secrets-scan.json
- run: |
if jq 'length > 0' secrets-scan.json | grep -q true; then
echo "::error::Hardcoded secret detected"
exit 1
fipython3 ${CLAUDE_PLUGIN_ROOT}/skills/scanning-for-hardcoded-secrets/scripts/scan_secrets.py \
/path/to/acquired-repo --include-tests --min-severity medium--include-tests is important here because legacy test fixtures
often contain real credentials someone forgot to redact.
JSON / JSONL / Markdown per lib/report.py. Exit codes: 0 clean, 1
high/critical, 2 error.
Matched strings are partially redacted in output (first 4 + last 4 chars visible, middle redacted) to avoid the scanner output itself becoming a leak surface.
<YOUR_KEY_HERE> →
the scanner skips strings containing <, >, EXAMPLE,
PLACEHOLDER, YOUR_, XXXX (configurable).references/THEORY.md — Per-credential-family threat model, why
each provider's keys are extracted by bots first, history-scrub
decision framework, entropy-detection theoryreferences/PLAYBOOK.md — Per-language migration patterns
(Python dotenv, Node .env+dotenv, Ruby Rails credentials, Go
envconfig), provider rotation procedures, GitHub secret-scanning
integration© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts, references) in skills/.curated/scanning-for-hardcoded-secrets of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Scanning For Hardcoded 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 |
|---|---|---|---|---|---|---|
| Scanning For Hardcoded Secrets this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.1k | Automated safety check: Notes | MIT | |
| Security SecretsIgorWarzocha/Opencode-Workflows | 122 | — | ~1.2k | Automated safety check: Notes | None | |
| Audit Env Variablesqdhenry/Claude-Command-Suite | 1.3k | — | ~2.8k | Automated safety check: Notes | None | |
| Secrets Managementdavila7/claude-code-templates | 33k | 12 repos | ~2k | Automated safety check: Pass | MIT | |
| Phase 9 Deploymentww-w-ai/bkit-claude-code | 601 | — | ~2.7k | Automated safety check: Notes | Apache-2.0 | |
| Atmos Authcloudposse/atmos | 1.4k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 |
IgorWarzocha/Opencode-Workflows
Review secret detection patterns and scanning workflows. An agent skill from IgorWarzocha/Opencode-Workflows.
qdhenry/Claude-Command-Suite
Analyze environment variables in JavaScript/TypeScript projects.
davila7/claude-code-templates
Secure secrets management practices for CI/CD pipelines using Vault, AWS Secrets Manager, and other tools.
ww-w-ai/bkit-claude-code
Deploy to production — CI/CD pipelines, environment config, deployment strategies.
cloudposse/atmos
Authentication and identity management: providers (SSO/SAML/OIDC/GCP/Atmos Pro), identities, keyring, identity chaining, login/exec/shell/console, and github/sts for private GitHub access
imbue-ai/latchkey
Interact with arbitrary third-party or self-hosted services (AWS, Slack, Google Drive, Dropbox, GitHub, GitLab, Linear, Coolify...) using their HTTP APIs.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Categories
Scan a source-code tree for hardcoded credentials embedded in source files: AWS access keys, GitHub tokens, Stripe keys, Slack tokens, Anthropic API keys, OpenAI keys, JWT signing secrets, generic…. Scanning For Hardcoded Secrets is an agent skill from jeremylongshore/tons-of-skills-marketplace. Scan a source-code tree for hardcoded credentials embedded in source files: AWS access keys, GitHub tokens, Stripe keys, Slack tokens, Anthropic API keys, OpenAI keys, JWT signing secrets, generic base64-encoded passwords, RSA / SSH private keys, and high-entropy string literals that pattern-match common credential shapes.
Scanning For Hardcoded Secrets fits situations like: : pre-commit gate before pushing a feature branch; audit before SOC2; post-incident scan after a leak; inheriting a codebase you didnt write.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill scanning-for-hardcoded-secrets -a claude-code`. Or copy the skill folder (skills/.curated/scanning-for-hardcoded-secrets in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/scanning-for-hardcoded-secrets in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill scanning-for-hardcoded-secrets -a codex`. Or copy the skill folder (skills/.curated/scanning-for-hardcoded-secrets in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/scanning-for-hardcoded-secrets in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill scanning-for-hardcoded-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/scanning-for-hardcoded-secrets, .gemini/skills/scanning-for-hardcoded-secrets, .github/skills/scanning-for-hardcoded-secrets and .opencode/skills/scanning-for-hardcoded-secrets in your project.
Going by SKILL.md and its folder, Scanning For Hardcoded Secrets needs Python for the scripts in its folder, the command-line tools its instructions call (python3, git and jq) and credentials named JWT_SECRET. Our summary lists: Python 3; A credential in JWT_SECRET. Its frontmatter pre-approves these tools: Read, Bash(python3:*), Glob, Grep. Compatibility (from SKILL.md): Designed for Claude Code.
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Scanning For Hardcoded Secrets is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Scanning For Hardcoded Secrets: Security Secrets (IgorWarzocha/Opencode-Workflows, 122 stars), Audit Env Variables (qdhenry/Claude-Command-Suite, 1.3k stars), Secrets Management (davila7/claude-code-templates, 33k stars) and Phase 9 Deployment (ww-w-ai/bkit-claude-code, 601 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.