Search: "safety"

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.

Systematic code maturity assessment using Trail of Bits' 9-category framework. Analyzes codebase for arithmetic safety, auditing practices, access controls, complexity, decentralization, documentation, MEV risks, low-level code, and testing, then produces a scorecard with evidence-based ratings and a priority-ordered roadmap. Use when assessing or scoring the maturity of a smart contract or blockchain codebase, producing a maturity scorecard or evaluation, or judging how mature, well-tested, or well-documented such a project is against a rubric.

Plans, configures, inspects, restarts, and analyzes bounded FluidSim computational-fluid-dynamics simulations with explicit numerical-validity and HPC safety checks. Use for FluidSim solver selection, parameter review, FFT/MPI setup, output diagnostics, or restart compatibility.

Develops and reviews PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Supports PyLabRobot protocols and API questions; keep physical execution behind an explicit operator safety gate.

Creates safety-bounded draft structures and runs local deterministic checks for clinical case, diagnostic, trial, safety, and aggregate research reports. Use only with synthetic, de-identified, or aggregate inputs and verified source-fact manifests; every output requires qualified review.

Performs comprehensive C/C++ security review for memory corruption, integer overflows, race conditions, and platform-specific vulnerabilities. Use when auditing native C/C++ applications, reviewing daemons or services for memory safety, or hunting integer overflow / use-after-free / race conditions in userspace code.

Performs comprehensive Rust security review for safe/unsafe boundary issues, memory safety in unsafe blocks, concurrency hazards, panic-induced DoS, FFI safety, and async runtime mistakes. Use when auditing Rust crates, services, or libraries — particularly those with `unsafe`, FFI, or concurrent code.

🔁 Finishes your entire backlog while you sleep. The AI orchestrator that DOES the work end-to-end on ANY LLM — discover → implement → verify → merge → 24/7 — behind safety gates, at up to 90% fewer tokens. 48 extension points. Not a chatbot. A worker.

The essential safety and workflow layer that every Claude Code user installs first and never thinks about again.

The safety brake for naked AI coding. A deterministic governance layer that lets N coding agents concurrently mutate one repo — via 5D CID identity, a 7-stage lifecycle, SHA256-anchored closure evidence, and atom maps that retire legacy modules through a gated replacement lifecycle.

Operating procedure for Adako, the MCP server and REST API that connects this assistant to the user's Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads accounts (TikTok Ads tools are listed but not available yet). Use it whenever the user asks about ad spend, performance, campaigns, ad sets, ad groups, keywords, search terms, audiences, budgets, pixels, creatives, monitors or briefs on those platforms, and whenever they ask to create, pause, resume, re-budget or otherwise change anything in those accounts. It defines the safety contract (read before write, every write becomes a proposal the user approves, created objects are always paused), the tool-call contract (233 tools, read routers for lookups and _write routers for changes, ids are strings, budgets are decimals in the account currency, dates are YYYY-MM-DD or a preset), the tool map per platform, and the standard workflows for performance reviews, wasted-spend cleanup, campaign launches, monitors, approvals and error recovery. Do not use it for platforms Adako does not cover.

Operating procedure for Adako, the MCP server and REST API that connects this assistant to the user's Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads accounts (TikTok Ads tools are listed but not available yet). Use it whenever the user asks about ad spend, performance, campaigns, ad sets, ad groups, keywords, search terms, audiences, budgets, pixels, creatives, monitors or briefs on those platforms, and whenever they ask to create, pause, resume, re-budget or otherwise change anything in those accounts. It defines the safety contract (read before write, every write becomes a proposal the user approves, created objects are always paused), the tool-call contract (233 tools, read routers for lookups and _write routers for changes, ids are strings, budgets are decimals in the account currency, dates are YYYY-MM-DD or a preset), the tool map per platform, and the standard workflows for performance reviews, wasted-spend cleanup, campaign launches, monitors, approvals and error recovery. Do not use it for platforms Adako does not cover.