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-contribute-integrationnpx skills add ory/claude-plugins --skill ory-contribute-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-contribute-integration)<a href="https://agentmods.dev/skills/ory/claude-plugins/ory-contribute-integration"><img src="https://agentmods.dev/badge/skills/ory/claude-plugins/ory-contribute-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.00124 | $0.01961 |
| Opus 5 | $0.00062 | $0.00981 |
| Sonnet 5 | $0.00025 | $0.00392 |
| Haiku 4.5 | $0.00012 | $0.00196 |
Grade A, and why
ory-contribute-integration scanned grade A with 0 findings 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 4d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contribute an Integration to ory/integrates
You are helping the user author a new integration and contribute it back to the
public ory/integrates repository ("Sample code and reference configuration for
integrating Ory Network with third-party products"). The deliverable is a pull
request against github.com/ory/integrates.
This skill carries the workflow. The template files live in the repo itself —
fetch them from github.com/ory/integrates (branch main) rather than
reproducing them, so they never drift.
Precondition:
ory/integratesmust be reachable (it is a public repo). Ifgh repo view ory/integratesor a fetch of a template file fails, tell the user the repo is unreachable and stop — do not fabricate template contents.
Step 0 — Open the "New integration" issue first
Ory asks contributors to open a New integration issue before the PR, so scope
is confirmed and the work isn't already in flight. Remind the user to do this
(GitHub → ory/integrates → Issues → "New integration" template) and capture the
issue number for the PR.
Step 1 — Get a checkout and pick the category
The contribution workflow happens inside a checkout of the repo:
gh repo clone ory/integrates
cd integrates
(or a fork, if the user will PR from their own remote.) Then choose the
category folder the integration belongs in — it must match an existing
top-level directory (crm/, api-gateways/, identity-verification/, mfa/,
enterprise-sso/, …). List them with ls -d */ | grep -v _examples.
Step 2 — Determine the integration type
Every integration is one of three types. Infer from intent; if unclear, ask directly.
| Signal from the user | Type | Template |
|---|---|---|
| Transform/enrich an identity at registration; gate or react to a self-service flow synchronously; call a vendor API during an Ory flow | webhook |
_examples/_template-webhook/ |
| Validate Ory JWTs at a gateway; Console-only setup; no handler code | config |
_examples/_template-config/ |
| React to events asynchronously; Ory Network Enterprise Live Event Stream consumer | http-event |
_examples/_template-http-event/ |
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.
- 4d ago First seen · 165 lines · 124 tokens per session scan A 780206360e5a
ory-contribute-integration is a skill published in the GitHub repository ory/claude-plugins (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 124 tokens to every session and 1,961 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. 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…