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-integrationnpx skills add ory/claude-plugins --skill ory-build-integrationgit 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-integration)<a href="https://agentmods.dev/skills/ory/claude-plugins/ory-build-integration"><img src="https://agentmods.dev/badge/skills/ory/claude-plugins/ory-build-integration.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.00139 | $0.01478 |
| Opus 5 | $0.00069 | $0.00739 |
| Sonnet 5 | $0.00028 | $0.00296 |
| Haiku 4.5 | $0.00014 | $0.00148 |
Grade A, and why
ory-build-integration scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL "$BASE/ory-actions.yaml" -o ory-integration/ory-actions.yaml How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build an Ory Integration Into Your App
You are helping the user wire an Ory Network integration into their own
application, reusing the proven patterns from the public ory/integrates
repository. There is no contribution, registry, Maintained by:, or DCO concern
here — you fetch the runnable subset of a template and adapt it in place.
This skill carries the workflow. The template files live in
github.com/ory/integrates (branch main); fetch the ones you need so they stay
current.
Precondition:
ory/integratesmust be reachable (public repo). If a fetch fails, tell the user and stop — do not fabricate handler code.
Step 1 — Determine the type and app context
Pick the integration type from intent; ask directly if unclear.
| Signal from the user | Type |
|---|---|
| Transform/enrich an identity at registration; gate or react to a flow synchronously; call a vendor API during an Ory flow | webhook |
| Validate Ory JWTs at a gateway; Console-only config; no handler code | config |
| React to events asynchronously; Ory Enterprise Live Event Stream consumer | http-event |
Also establish: the app's framework/runtime, where the handler will live, and how it's deployed (these decide where you write files and how you mount the route).
Step 2 — Fetch the runnable subset
Pull only the files the user needs from _examples/_template-<type>/. Prefer raw
fetch so you don't clone the whole repo into the user's project.
Raw file fetch (base URL
https://raw.githubusercontent.com/ory/integrates/main/_examples/_template-<type>/):
BASE=https://raw.githubusercontent.com/ory/integrates/main/_examples/_template-webhook
mkdir -p ory-integration/webhook ory-integration/jsonnet
curl -fsSL "$BASE/ory-actions.yaml" -o ory-integration/ory-actions.yaml
curl -fsSL "$BASE/jsonnet/identity.jsonnet" -o ory-integration/jsonnet/identity.jsonnet
curl -fsSL "$BASE/webhook/server.ts" -o ory-integration/webhook/server.ts
curl -fsSL "$BASE/webhook/package.json" -o ory-integration/webhook/package.json
curl -fsSL "$BASE/webhook/tsconfig.json" -o ory-integration/webhook/tsconfig.json
curl -fsSL "$BASE/webhook/.env.example" -o ory-integration/webhook/.env.example
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 · 109 lines · 139 tokens per session scan A 53f89af71920
ory-build-integration is a skill published in the GitHub repository ory/claude-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 139 tokens to every session and 1,478 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…