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>
Audit Context Building
Build deep architectural context through ultra-granular code analysis before vulnerability hunting.
Author: Omar Inuwa
When to Use
Use this skill when you need to:
- Develop deep comprehension of a codebase before security auditing
- Build bottom-up understanding instead of high-level guessing
- Reduce hallucinations and context loss during complex analysis
- Prepare for threat modeling or architecture review
What It Does
This skill governs how Claude thinks during the context-building phase of an audit. When active, Claude will:
- Perform line-by-line / block-by-block code analysis
- Apply First Principles, 5 Whys, and 5 Hows at micro scale
- Build and maintain a stable, explicit mental model
- Identify invariants, assumptions, flows, and reasoning hazards
- Track cross-function and external call flows with full context propagation
Key Principle
This is a pure context building skill. It does NOT:
- Identify vulnerabilities
- Propose fixes
- Generate proofs-of-concept
- Assign severity or impact
It exists solely to build deep understanding before the vulnerability-hunting phase.
Installation
/plugin install trailofbits/skills/plugins/audit-context-building
Phases
- Initial Orientation - Map modules, entrypoints, actors, and storage
- Ultra-Granular Function Analysis - Line-by-line semantic analysis with cross-function flow tracking
- Global System Understanding - State/invariant reconstruction, workflow mapping, trust boundaries
Anti-Hallucination Rules
- Never reshape evidence to fit earlier assumptions
- Update the model explicitly when contradicted
- Avoid vague guesses; use "Unclear; need to inspect X"
- Cross-reference constantly to maintain global coherence
Related Skills
issue-writer- Write up findings after context is builtdifferential-review- Uses context-building for baseline analysisspec-compliance- Compare understood behavior to documentation