Use when performing security-focused vulnerability research, bug bounty hunting, penetration testing, or exploit development on a specific target codebase or binary. Covers taint analysis across 30+ attack domains, sink analysis for 10+ languages, SAST/DAST integration, agent sweep, DuckDB-persisted phase pipeline…
Use when improving Lighthouse scores, reducing page load times, debugging performance bottlenecks, optimizing Core Web Vitals for SEO, or implementing modern browser performance APIs like View Transitions and Speculation Rules.
Use when directing LLM coding agents on substantial development tasks — establishing executable oracles, designing agent playbooks, constraining agent output quality, or preventing metric gaming. Also use when LLM-generated code has recurring quality or architecture issues that need systematic correction. Triggers…
Use when building, configuring, deploying, or troubleshooting ZeroClaw AI agent infrastructure — including provider setup, channel binding, memory backends, config.toml authoring, CLI usage, Docker/native runtime, and migration from other agent frameworks.
Use when creating or editing Obsidian Spaced Repetition flashcards, organizing decks, starting card or whole-note reviews, inspecting scheduling metadata, or troubleshooting missing cards through the official Obsidian CLI. Covers st3v3nmw/obsidian-spaced-repetition, cloze cards, #flashcards, #review, and obsidian…
Use when writing or reviewing performance-sensitive Rust, profiling slow Rust code, reducing allocations, investigating latency or throughput regressions, or diagnosing bloated binaries and long compile times. Covers allocation, iterators, data layout, hashing, async/concurrency, build profiles, Clippy review gates…
Use when running or reporting ML experiments on rented Vast.ai GPU instances — diagnosing strict FP32 equivalence checks that pass on CPU but fail on CUDA (cuDNN TF32), parsing JSON metrics collected over SSH, and keeping held-out/test-scope reporting accurate.
Use when you want to fuzz any software target — library, compiler, interpreter, parser, kernel/syscall, DB engine, SMT solver, binary/file format, or network protocol — by priming an LLM with that target's HISTORICAL bug-triggering code to generate unusual, edge-case inputs (history-driven LLM fuzzing).…
Use when adding GitLab MRs to the Hermes watcher on ssh-vhs, editing or redeploying watchgitlabmrfindings.py, diagnosing missed/duplicate MR status messages in Telegram, or verifying the Hermes no-agent cron.
Use when writing or improving Jev programs — the TypeSafe judgment model behind POST /v1/systemone. Covers primitive selection (noul, choice, score), instruction and criteria writing, minimal state and token budgets, the raw HTTP API, confidence-gated composition, speculative fan-out, and the symptom-to-fix revision…
Use when turning a real project's git history into a labeled, enriched, leakage-free security-fix dataset ("oracle") for a vulnerability classifier, rule-authoring feed, or risk-prioritization model. Triggers: "mine commits for security fixes", "build a vuln dataset / training corpus from git history", "label commits…
Use when creating, repairing, testing, or reviewing OpenGrep YAML rules, porting Semgrep rules, or modeling sources, sinks, sanitizers, and propagators. Apply procedural-first augmentation, claim-specific semantics, test-first fixtures, and false-positive/false-negative regression gates. Includes four complete…
Use when designing or reviewing Rust public APIs, trait boundaries, builders, newtypes, typestate transitions, enum versus dyn dispatch, or applying SOLID and creational, structural, or behavioral design patterns without class hierarchies. Triggers include dyn compatibility, dependency injection, API evolution…
Use when implementing or debugging Rust threads, Send/Sync bounds, Arc and synchronization, channels, Tokio async tasks, cancellation, graceful shutdown, backpressure, deadlocks, or choosing Rayon for CPU-bound parallel work.
Use when writing, refactoring, or reviewing Rust against API and engineering guidelines, auditing crate readiness, or defining ownership, error, safety, and allocation contracts. Covers naming, public APIs, interoperability, documentation, macros, and verification. Not a Rust tutorial or profiling playbook.
Use when writing or reviewing ordinary Rust, fixing move/borrow/lifetime errors, handling Option or Result, choosing standard-library string/iterator/I/O APIs, or configuring Cargo workspaces, rustfmt, Clippy, and rust-analyzer. Covers UTF-8, partial moves, allocation semantics, and production error propagation; use…
Use when writing or debugging Rust macrorules! matchers, repetitions, hygiene, $crate exports, edition-dependent fragments, or procedural derive, attribute, and function-like macros using syn and quote; includes expansion and diagnostic tests.
Use when implementing Rust features test-first, reproducing Rust bugs with regression tests, characterizing legacy Rust, or applying red-green-refactor with cargo test. Covers boundary and equivalence cases, proptest shrinking, mockall expectations, rstest fixtures, async/concurrent/CLI tests, and coverage…
Use when writing or reviewing Rust unsafe blocks, raw-pointer abstractions, MaybeUninit or manual Drop code, unsafe trait implementations, or C/C++ FFI bindings. Covers pointer validity, aliasing and provenance, C ABI/layout, callbacks, allocator ownership, C strings, unwinding, Rust 2024 unsafe syntax, and…
Use when compiling Rust to WebAssembly, integrating wasm-bindgen or web-sys with browser JavaScript and the DOM, packaging with wasm-pack, choosing wasm32-unknown-unknown versus wasm32-wasip1 or wasm32-wasip2, designing WIT component interfaces, or debugging Wasm loading, capabilities, and target tests.
★not rated 2 4d agoA73 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: