Results for “trail-of-bits”

---

Orchestrate cross-chain swaps, bridges, and DeFi yield deposits via the Sequence Trails API, with on-chain execution through Bankr.

Tracks crypto and AI narratives with mindshare scores, velocity arrows, phase labels, named drivers, and position calls. Detects phase transitions and reflexivity signals.

Use when building a cursor trail whose spacing stays constant at any hand speed by emitting motes per distance travelled (not on a timer)—sub-segment placement, ring-buffer ordering, idle breath, 3D screen anchoring, coasting, touch and reduced-motion fallbacks—for wisps, sparks, embers, comet tails, plankton, or dust.

Runs a Trailmark summary analysis on a codebase to auto-detect languages, count entry points, and list dependencies.

Expert in creating opening lines, thumbnails, and hooks that stop the scroll. Covers curiosity gaps, pattern interrupts, emotional triggers, and platform-specific hooks. Knows how to earn attention in the first 3 seconds without resorting to clickbait. Use when "hook, opening line, scroll stopper, headline, first line, attention grab, thumbnail, clickable, " mentioned.

Hunt for adversary abuse of Living Off the Land Binaries (LOLBins) by analyzing endpoint process creation logs for suspicious execution patterns of legitimate Windows system binaries used for malicious purposes.

Proactively hunt for adversary abuse of legitimate system binaries (LOLBins) to execute malicious payloads while evading detection.

Detect abuse of legitimate Windows binaries (LOLBins) used for living off the land attacks by monitoring process creation, command-line arguments, and parent-child relationships.

Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.

Investigates bugs, regressions, and crashes by dispatching four parallel read-only sub-agents, then ranks hypotheses and recommends the fastest proof or fix path.

Trace deprecated shim

Select alternative execution paths when a plan step fails — branch on outcomes instead of blind retry. Load when a structured plan step fails, an unexpected observation arrives, or the user asks what to try next after an error. Also triggers on "try another approach", "route around this failure", "replan on failure", "if X fails try Y", or outcome-based branching during multi-step work. Pairs with structured-planning and debug-and-fix. Does not replace root-cause debugging — adds plan-level path selection.

Reviews and repairs risky or unclear code with minimal validated changes, running a fixed-point loop until the diff is clean across two consecutive review cycles.

Generates at most one token recommendation and one prediction-market pick per run, each with a falsifiable thesis, entry, sizing, and kill criterion. Returns NO_PICK when no candidate meets the bar.

Find adjacent vendors and subs (not top market primes) who fill a capability gap against a displacement target using USASpending flows and SAM entity signals. Use when user defines a teaming gap and wants vault-ready partner shortlist with citations.

Runs a relentless interview that asks every frontier question at once, round by round. Use when the user wants to be grilled on a design or map a design tree.

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.

Synthesize retrospectives into themes, root causes, decisions, and team improvements.