Proteus

Coordinate disciplined, continuous, professional vulnerability research with Proteus memory, campaigns, bounded delegation, validation gates, realistic exploitability, anti-slop controls, and report-grade decision discipline.

Operate as a secondary OpenCode-backed Proteus Chimera agent with coordinator-controlled scope, communication, snapshots, labs, and permissions.

Coordinate Proteus continuous vulnerability research with memory, campaigns, delegation, validation gates, and report-grade discipline.

Develop non-obvious Proteus exploit chains from primitives, side effects, state drift, and component coupling.

Compress Proteus campaign or round state into a concise checkpoint with facts, killed paths, pivots, and next moves.

Map a codebase for Proteus research through architecture, dataflow, trust boundaries, invariants, and high-ROI branch material.

Design calibrated Proteus fuzzing and differential probes that learn input behavior instead of spraying generic payloads.

Build realistic Proteus PoC plans, labs, negative controls, and exploitability evidence for concrete candidates.

Gather Proteus security intelligence for known status, timelines, advisories, changelogs, docs, and duplicate risk.

Conduct authorized Proteus web research with campaign memory, chaining, fuzzing, intel, and PoC heuristics.

Build realistic local/OSS-authorized PoC plans, labs, manual blackbox reproduction steps, negative controls, and exploitability evidence for Proteus candidates with concrete signal.

Develop non-obvious exploit chains from concrete primitives, side effects, trust-boundary drift, state transitions, component coupling, and capability amplification. Use when a Proteus branch needs creative offensive reasoning beyond the obvious direct bug path.

Compress Proteus campaign or round state after meaningful progress, preserving confirmed facts, killed paths, pivots, branch scores, learned heuristics, unresolved blockers, and the next high-ROI move.

Perform deep offensive codebase research for Proteus by mapping architecture, dataflow, trust boundaries, invariants, side effects, recent change risk, and high-ROI branch material. Use when Codex must understand a codebase before chaining, fuzzing, Cicada, or PoC work.

Design calibrated fuzzing, differential probes, harnesses, and oracles for narrow Proteus surfaces. Use when the goal is to learn how inputs affect parsers, state machines, adapters, runtimes, or side effects, not to spray generic payloads.

Gather security intelligence for Proteus hypotheses: expected behavior, public-known status, advisories, changelogs, issues, PRs, docs, tests, affected-version timeline, duplicate risk, and research pivots. Use when a branch needs external truth, not active web exploitation.

Conduct authorized web application research for Proteus targets using the same campaign, chaining, fuzzing, intel, and PoC heuristics adapted to live or local web surfaces. Use for endpoint behavior mapping, blackbox probes, browser/API workflows, and web pentest-style validation.