mirror of
https://github.com/trailofbits/skills
synced 2026-06-21 14:12:00 +00:00
Lixin2026
d5fe2e6a78
* feat(codex): add skill UI metadata * Use official Trail of Bits logo * fix: resolve code review findings for PR #175 Codex silently drops the icons as authored: its loader (codex-rs/core-skills resolve_asset_path) requires icon paths containing '..' to resolve under <plugin_root>/assets/, and the repo-root .codex/assets location fails that containment check. Verified empirically via codex app-server plugin/read: every iconSmall/iconLarge came back null; only brand_color applied. P1 fixed: - Vendor trail-of-bits-mark.svg into plugins/<name>/assets/ for all 38 plugins with skills and point every openai.yaml at ../../assets/trail-of-bits-mark.svg (the supported plugin-level shared asset pattern). Icons now resolve for marketplace installs too, since nothing escapes the plugin root. - Drop the .codex/ additions: .codex/skills/gh-cli/agents/ openai.yaml resolved nowhere (.codex/skills is not a Codex discovery root) and PR #173 removes the whole .codex/ tree P2 fixed: - Patch-bump all 38 touched plugins in plugin.json and marketplace.json so installed clients pick up the metadata Verified: - Static check replicating Codex's resolution algorithm: all 73 yaml files resolve under their plugin assets/ and exist - Live codex app-server probe: 71/72 loadable skills report resolved iconSmall/iconLarge and brand_color #D83A34 (claude-in-chrome-troubleshooting fails to load on main due to a pre-existing 64-char qualified-name limit, fixed by #173's rename; zeroize-audit's manifest mcpServers object is likewise a pre-existing Codex incompatibility fixed by #173) - validate_codex_skills.py, validate_plugin_metadata.py, prek all pass Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(codex): use skill-local icon assets --------- Co-authored-by: Dan Guido <dan@trailofbits.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Insecure Defaults Detection
Security skill for detecting insecure default configurations that create vulnerabilities when applications run with missing or incomplete configuration.
Overview
The insecure-defaults skill helps identify security vulnerabilities caused by:
- Hardcoded fallback secrets (JWT keys, API keys, session secrets)
- Default credentials (admin/admin, root/password)
- Weak cryptographic defaults (MD5, DES, ECB mode)
- Permissive access control (CORS *, public by default)
- Missing security configuration that causes fail-open behavior
Critical Distinction: This skill emphasizes fail-secure vs. fail-open behavior. Applications that crash without proper configuration are safe; applications that run with insecure defaults are vulnerable.
Installation
cd parent-folder/skills
/plugin install ./plugins/insecure-defaults
Or from the plugin marketplace:
/plugin install insecure-defaults
When to Use
Use this skill when:
- Security auditing production applications or services
- Configuration review of deployment manifests (Docker, Kubernetes, IaC)
- Pre-production checks before deploying new services
- Code review of authentication, authorization, or cryptographic code
- Environment variable handling analysis for secrets management
- API security review checking CORS, rate limiting, authentication
- Third-party integration review for hardcoded test credentials
Usage
Audit this codebase for insecure defaults—focus on environment variable fallbacks and authentication configuration