Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/ory/claude-plugins/ory-build-agentnpx skills add ory/claude-plugins --skill ory-build-agentgit clone --depth 1 https://github.com/ory/claude-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ory/claude-plugins/ory-build-agent)<a href="https://agentmods.dev/skills/ory/claude-plugins/ory-build-agent"><img src="https://agentmods.dev/badge/skills/ory/claude-plugins/ory-build-agent.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00204 | $0.03879 |
| Opus 5 | $0.00102 | $0.01939 |
| Sonnet 5 | $0.00041 | $0.00776 |
| Haiku 4.5 | $0.00020 | $0.00388 |
Grade B, and why
ory-build-agent scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
r = await httpx.post("http://localhost:5310/gate", How it starts
The opening of the file, as written. The whole thing — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
Precondition: the user has an Ory project (or will spin up the local stack — see
/project:ory-local-dev) and has the env vars from/project:ory-auth-setupfigured out. Do not fabricate credentials or scaffold a project on their behalf.
Step 1 — Pick the SDK and confirm the agent shape
Ask the user which SDK they're using and what the agent looks like. Below are the SDKs this skill carries explicit recipes for. Others (LangChain, LlamaIndex, generic OpenAI tool-calling loops) follow the same pattern — wrap each tool dispatch with the gate from Step 4.
| SDK | Language | Where Ory hooks in |
|---|---|---|
Claude Agent SDK (@anthropic-ai/claude-agent-sdk) |
TypeScript / Python | canUseTool callback on query({...}) |
OpenAI Agents SDK (@openai/agents) |
TypeScript | Per-tool execute wrapper or RunHooks.onToolStart |
| Salesforce Agentforce (Agent Builder) | declarative + Apex | External Service / side-car — see "Salesforce" below |
Mastra (@mastra/core) |
TypeScript | Higher-order wrapper around each tool's execute |
Mistral AI (@mistralai/mistralai / mistralai) |
TypeScript / Python | Per-tool wrapper inside the chat-completion loop or the Agents API tool registry |
PydanticAI (pydantic-ai) |
Python | @agent.tool decorator stack |
Vercel AI SDK (ai) |
TypeScript | Higher-order wrapper at streamText({ tools }) |
LangGraph (langgraph) |
Python / TypeScript | ToolNode wrapper or RunnableLambda per tool |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 389 lines · 204 tokens per session scan B 117379cf8379
ory-build-agent is a skill published in the GitHub repository ory/claude-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 204 tokens to every session and 3,879 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it B with 1 finding (sends data to an external url). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…