trailofbits · Agent Skills
出典を確認した実質的な文書を持つ Skill が 98 件あります。カードを開くと原文、パッケージ内容、導入方法を確認できます。
libfuzzer
Sets up and runs libFuzzer, the coverage-guided fuzzer built into LLVM, on C/C++ code that compiles with Clang. Covers harness structure, -fsanitize=fuzzer builds, corpus and dictionary management, sanitizer integration, and campaign triage. Use when writing or debugging an LLVMFuzzerTestOneInput harness, starting fuzzing on a C/C++ library, choosing between libFuzzer and AFL++, or working out why a libFuzzer run finds nothing.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
mermaid-to-proverif
Translates Mermaid sequenceDiagrams describing cryptographic protocols into ProVerif formal verification models (.pv files). Use when generating a ProVerif model, formally verifying a protocol, converting a Mermaid diagram to ProVerif, verifying protocol security properties (secrecy, authentication, forward secrecy), checking for replay attacks, or producing a .pv file from a sequence diagram.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
mutation-testing
Configures mewt or muton campaigns, analyzes surviving mutants, and investigates bugs exposed by testing gaps. Use when setting up mutation testing, reviewing campaign results, identifying equivalent mutants, or finding bugs from surviving mutations.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
ossfuzz
Enrolls a project in OSS-Fuzz, Google's free continuous fuzzing service for open source, and drives it locally. Covers project.yaml, Dockerfile and build.sh setup, the helper scripts, reproducing OSS-Fuzz crash reports, and the acceptance criteria. Use when setting up continuous fuzzing for an open-source project, reproducing an OSS-Fuzz bug report, or testing an OSS-Fuzz build before submitting it.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
patching-bugs
Use when a known bug or falsifiable bug hypothesis in a local codebase needs a patch commit and reviewable proof report.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
post-patch-validation
Validates security patches with reproducible baseline-versus-patched evidence, including original exploits, root-cause variants, behavior preservation, regressions, and newly introduced security failures. Use after a patch exists and before accepting, merging, or reporting it as fixed; also use when an AI-generated patch, remediation commit, pull request, or proposed upstream fix needs adversarial post-patch validation across any language.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
pr-improver
Runs an autonomous review-and-fix improvement loop over the current branch's changes until a PR review comes back clean, scoped mechanically to the directories the branch touched. Reviews are performed by an installed PR-review skill (default: pr-review-toolkit's review-pr). Use to fix review findings on a branch before opening or updating a pull request ('clean up this branch', 'fix this PR until review passes', 'run review-and-fix on my changes'). NOT for a one-time review — run the PR-review
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
prepare-regression
Use when pinning before/after sources and collecting PR or commit context for a regression investigation.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
prove-patch
Use when a local security patch commit needs independent scoped and three-arm proof.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
regression-hunt
Use when investigating regressions in PRs or commits, coordinating a regression campaign, or resuming saved progress.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
replay-regression
Use when independently verifying a supplied PoC against fresh live before/after deployments.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
report-regressions
Use when assembling or refreshing an evidence-linked regression report from saved campaign decisions.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
reproduce-bug
Use when a named runtime or compiler bug in a local repository needs independent reproduction.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
reproduce-regression
Use when deploying before/after systems and building a live-system PoC for a regression candidate.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
review-walkthrough
Generates an interactive HTML walkthrough for reviewing code changes. Use only when explicitly called.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
ruzzy
Sets up and runs Ruzzy, Trail of Bits' coverage-guided Ruby fuzzer and the only production-ready one for the language. Covers harness structure, fuzzing pure Ruby and the native C extensions in gems, and sanitizer builds. Use when fuzzing a Ruby library or gem, testing a Ruby C extension for memory safety, or asking how to fuzz Ruby at all.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
sarif-parsing
Parses and processes SARIF files from static analysis tools like CodeQL, Semgrep, or other scanners. Triggers on "parse sarif", "read scan results", "aggregate findings", "deduplicate alerts", or "process sarif output". Handles filtering, deduplication, format conversion, and CI/CD integration of SARIF data. Does NOT run scans — use the Semgrep or CodeQL skills for that.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
second-opinion
Gets independent code reviews from Codex or Antigravity for uncommitted changes, branch diffs, and commits. Use when the user requests an external review, a second opinion on code, a codex review, a gemini review, an antigravity review, or /second-opinion.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
semgrep
Runs a Semgrep security scan over a codebase: detects languages, selects rulesets, presents the plan for explicit approval, then runs every approved ruleset through scripts/run-scans.sh, which batches the semgrep processes and writes scans.json, and merges the output to SARIF. Supports two scan modes, "run all" for full ruleset coverage and "important only" for security findings at medium-to-high confidence and impact. Uses Semgrep Pro for cross-file taint analysis when it is available. Use when
- 1時間の導入数
- 3
- GitHub Stars
- 8234
- 更新日
- 11月12日
semgrep-rule-creator
Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Use when writing Semgrep rules or building custom static analysis detections.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
skill-improver
Runs an autonomous review-and-fix improvement loop over a Claude Code skill until a review comes back clean, with a cross-round findings ledger, escalation when fixes stop converging, and a mechanical scope guard. Reviews are performed by the plugin-dev skill-reviewer agent. Use to fix skill quality issues, iteratively refine a skill, or resume a loop after an escalation ('fix my skill', 'improve this skill until it passes review', 'skill improvement loop'). NOT for a one-time review — use the p
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
slicing-code-context
Selects bounded, graph-informed source slices with Trailmark and delegates focused code analysis or patch-proposal work to a smaller subagent. Use when offloading function-, class-, caller-, callee-, call-path-, entrypoint-, or line-focused code tasks to constrained or locally hosted models without exposing the full repository.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日
solana-vulnerability-scanner
Scans Solana programs for 6 critical vulnerabilities including arbitrary CPI, improper PDA validation, missing signer/ownership checks, and sysvar spoofing. Use when auditing Solana/Anchor programs.
- 1時間の導入数
- 3
- GitHub Stars
- 8330
- 更新日
- 11月21日