ory-build-agent
Installation
SKILL.md
Build your own agent with @ory/argus
You are helping the user wire Ory Identities, Permissions, and activity auditing into an agent they are building themselves. They are not extending Claude Code, Codex, or one of the other harness plugins — they own the agent loop and choose where to intercept tool calls.
The integration is the same three moves regardless of SDK:
- Session start.
sessionStart(client, …)runs user and agent identity, delegation, permission-mode warming, and fail-open handling. - Permission check on every tool call. Wrap the SDK's tool dispatch with
gate(client, …)and translateresult.blockedinto the SDK's veto signal. - Completion. Call
complete(client, …)after the tool returns.
@ory/argus ships every helper and handles fail-open semantics (network
errors, rate limits, unconfigured project → allow). The SDKs differ only in
where that wrapper goes.