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-local-devnpx skills add ory/claude-plugins --skill ory-local-devgit clone --depth 1 https://github.com/ory/claude-pluginsWhat 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.00134 | $0.02367 |
| Opus 5 | $0.00067 | $0.01184 |
| Sonnet 5 | $0.00027 | $0.00473 |
| Haiku 4.5 | $0.00013 | $0.00237 |
Grade A, and why
ory-local-dev 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 yesterday.
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 -H "X-Session-Token: $KRATOS_SESSION_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build an Auth App Against a Local Ory Stack
You are helping the user develop an authentication application against a
local Ory stack running in Docker — not against Ory Network. The
@ory/claude-code plugin ships two commands that
manage the lifecycle:
/ory-agent-plugin:local-up— start Kratos, Keto, Hydra, and an Nginx gateway, then seed a test identity, session, and permission tuples./ory-agent-plugin:local-down— stop all services while preserving data volumes.
Both delegate to npx -y -p @ory/claude-code ory-claude local <subcommand>, so the same
workflow runs from the shell when the command shortcuts are not available.
When to use this skill
Pick the local stack over Ory Network when any of these are true:
- The user has no Ory Network project yet and wants to prototype.
- The user is working offline or behind an egress restriction.
- The user wants deterministic, throwaway test data they can reset
freely (
local reset). - The user is writing automated tests that hit a real Ory backend.
If the user already has an Ory Network project and just wants their
production app wired up, prefer the /project:ory-auth-setup skill and
point the SDK at the Network URL instead.
What /ory-agent-plugin:local-up gives you
After /ory-agent-plugin:local-up completes:
| Service | URL | Purpose |
|---|---|---|
| Gateway | http://localhost:4000 |
Unified API (mirrors Ory Network) |
| Agent Security | https://agents.console.ory:8080 |
Canonical permission/delegation broker |
| Kratos public | http://localhost:4433 |
Self-service flows (login, etc.) |
| Kratos admin | http://localhost:4434 |
Identity & session admin |
| Keto read | http://localhost:4466 |
Permission checks |
| Keto write | http://localhost:4467 |
Relation tuple writes |
| Hydra public | http://localhost:4444 |
OAuth2 / OIDC |
| Hydra admin | http://localhost:4445 |
OAuth2 client management |
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.
- yesterday First seen · 217 lines · 134 tokens per session scan A e650282227b8
ory-local-dev is a skill published in the GitHub repository ory/claude-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 134 tokens to every session and 2,367 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…