> browse/registry

> sponsor-finder

Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors. Uses deps.dev API for dependency resolution across npm, PyPI, Cargo, Go, RubyGems, Maven, and NuGet. Checks npm funding metadata, FUNDING.yml files, and web search. Verifies every link. Shows direct and transitive dependencies with OSSF Scorecard health data. Invoke with /sponsor followed by a GitHub owner/repo (e.g. "/sponsor expressjs/express").

> polyglot-test-agent

Generates comprehensive, workable unit tests for any programming language using a multi-agent pipeline. Use when asked to generate tests, write unit tests, improve test coverage, add test coverage, create test files, or test a codebase. Supports C#, TypeScript, JavaScript, Python, Go, Rust, Java, and more. Orchestrates research, planning, and implementation phases to produce tests that compile, pass, and follow project conventions.

> rust-mcp-server-generator

Generate a complete Rust Model Context Protocol server project with tools, prompts, resources, and tests using the official rmcp SDK

> harness-writing

The agent writes and improves fuzzing harnesses — the entrypoint functions that receive random data from fuzzers and route it to the system under test (SUT). It implements LLVMFuzzerTestOneInput for C/C++ with libFuzzer and AFL++ persistent mode, fuzz_target! macros for Rust with cargo-fuzz and the arbitrary crate, and go-fuzz Fuzz functions for Go. The agent structures inputs using FuzzedDataProvider, applies interleaved fuzzing patterns for multi-operation targets, handles input size validatio

> testing-handbook-skills

Application security testing toolkit from the Trail of Bits Testing Handbook. Helps the agent set up fuzzing campaigns, write fuzz harnesses, run coverage-guided fuzzers (libFuzzer, AFL++, cargo-fuzz, Atheris, Ruzzy), and triage crashes. Covers memory-safety sanitizers (AddressSanitizer, UBSan, MSan), static analysis with Semgrep and CodeQL, cryptographic validation using Wycheproof test vectors, and constant-time verification. Use when testing C, C++, Rust, Python, or Ruby code for vulnerabilit

> fuzzing-obstacles

The agent patches the system under test (SUT) to overcome common fuzzing obstacles using conditional compilation. It bypasses checksum and hash verification, replaces non-deterministic PRNG seeding with fixed seeds, skips complex multi-stage validation, and provides safe default values to prevent false positives. The agent uses FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION in C/C++ and cfg!(fuzzing) in Rust to ensure patches apply only during fuzzing builds. It applies this technique when coverage re

> fuzzing-dictionary

The agent creates and manages fuzzing dictionaries containing domain-specific tokens, magic bytes, protocol keywords, and format-specific strings to guide mutation-based fuzzers past early validation checks. It generates dictionary entries from header files, binary strings, man pages, and LLM prompts, and passes them to libFuzzer via -dict=, AFL++ via -x, or cargo-fuzz. The agent applies this technique when fuzzing parsers (JSON, XML, config files), protocol handlers (HTTP, DNS), file format pro

> libafl

The agent uses LibAFL, a modular Rust fuzzing library, to build custom fuzzers with fine-grained control over observers, feedback mechanisms, mutators, schedulers, and executors. It supports drop-in libFuzzer replacement mode via libFuzzer.a, fully custom fuzzer construction with InProcessExecutor and coverage-guided feedback, multi-core fuzzing with Launcher, crash deduplication via BacktraceObserver, and dictionary-based token mutations. The agent applies LibAFL when standard fuzzers like libF

> ossfuzz

The agent uses OSS-Fuzz, Google's free distributed continuous fuzzing platform, to build, run, and manage fuzzing infrastructure for open-source projects. It configures project enrollment files (project.yaml, Dockerfile, build.sh), builds fuzzers locally with helper.py, runs harnesses with AddressSanitizer and other sanitizers, generates coverage reports, and troubleshoots build failures. The agent applies this technique when setting up continuous fuzzing for C/C++, Rust, Python (Atheris), or Go

> cargo-fuzz

cargo-fuzz is the primary fuzzing tool for Rust projects built with Cargo. It enables developers to set up fuzz testing, write fuzz harnesses, and run fuzzing campaigns using the libFuzzer backend. Covers installation, harness writing, structure-aware fuzzing with the arbitrary crate, sanitizer integration including AddressSanitizer, coverage analysis, seed corpus management, and troubleshooting common issues. Useful when a developer needs to fuzz Rust code, find memory bugs, test parsers, or im

> gtars

High-performance toolkit for genomic interval analysis in Rust with Python bindings. Use when working with genomic regions, BED files, coverage tracks, overlap detection, tokenization for ML models, or fragment analysis in computational genomics and machine learning applications.

> review-rust-docs

Review the documentation of a Rust crate to ensure it meets our requirements and standards. Use this when you have done changes to Rust code.

> port-c-module

Guide for porting a C module to Rust. Use this when starting to port a C module to Rust.

> run-python-tests

Run end-to-end Python tests after making changes to verify correctness. Use this when you want to verify your changes from an end-to-end perspective, after ensuring the build and Rust tests pass.

> rust-tests-guidelines

Guidelines for writing Rust tests. Use this when you want to write Rust tests.

> check-rust-coverage

Check which Rust lines are not covered by Rust tests. Use this when you developed new Rust code and want to ensure it is tested.

> minimize-rust-ffi-crate-surface

Remove Rust-defined C symbols that are either unused or only used in C/C++ unit tests. Use this when you are refactoring a Rust FFI crate and want to remove unused symbols.

> run-rust-benchmarks

Run Rust benchmarks and compare performance with the C implementation. Use this when you work on migrating C code to Rust and want to ensure performance is not regressed.

> rust-docs-guidelines

Guidelines for writing Rust documentation. Use this when you want to write Rust documentation.

> rust-review

Review Rust code changes for unsafe correctness, documentation quality, and C-to-Rust porting fidelity. Use this when you want to review Rust changes before merging.