Use when: designing C ABI APIs with opaque types and function pointer tables, creating header-only C++ wrappers over C APIs, adding new API surface area to the SDK, reviewing ABI stability, implementing vtable-based versioned interfaces, wrapping opaque handles with RAII C++ classes.
Use when: writing or modifying JavaScript or TypeScript code in the Foundry Local SDK, implementing or maintaining the Node-API C addon for the JS SDK, porting C# or Python SDK functionality to JS/TS, wrapping native handles in idiomatic JS classes, implementing async iterables for streaming, packaging with…
Agent "red-team" from Miosa-osa/OSA, covering red team — adversarial review, default territory, read-only on all source code (every file in the repo), can write to and responsibilities.
Exploit and payload developer — writes custom exploits, reverse shells, bypasses, and PoCs for discovered vulnerabilities. Specializes in turning vulnerability findings into working attack code.
Use when something is broken and the cause isn't obvious — bugs, error stack traces, "works in dev not prod", performance regressions, weird behavior after a change.
Use for any task requiring external research — finding documentation, comparing libraries, looking up release notes, market research, fact-checking. Read-only by design — won't modify files. Auto-delegate when query starts with "find", "research", "look up", "compare", "what is the latest".
Use to review code changes (diffs, PRs, single files) for bugs, security issues, performance problems, style violations, and missing edge cases. Read-only — produces a review, doesn't fix code.