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-login-flownpx skills add ory/claude-plugins --skill ory-login-flowgit 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-login-flow)<a href="https://agentmods.dev/skills/ory/claude-plugins/ory-login-flow"><img src="https://agentmods.dev/badge/skills/ory/claude-plugins/ory-login-flow.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.00091 | $0.04786 |
| Opus 5 | $0.00046 | $0.02393 |
| Sonnet 5 | $0.00018 | $0.00957 |
| Haiku 4.5 | $0.00009 | $0.00479 |
Grade A, and why
ory-login-flow 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 -i "$NEXT_PUBLIC_ORY_SDK_URL/self-service/login/browser" How it starts
The opening of the file, as written. The whole thing — 559 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Auth Pages with Ory Elements
You are building login, registration, recovery, verification, and settings pages using Ory Elements — a prebuilt UI component library that renders Ory's self-service flows.
Default rule: every page in this guide is rendered with Ory Elements.
Do not hand-roll forms from flow.ui.nodes unless the user has
explicitly opted out after seeing the Ory Elements path. Custom node
rendering belongs in the fallback section at the end of this skill.
Why Ory Elements
- One component per flow (
<Login>,<Registration>,<Recovery>,<Verification>,<Settings>) covers the entire self-service surface. - Handles CSRF tokens, error messages, multi-step states, social buttons, passkeys, and MFA prompts automatically.
- New node types and flow capabilities ship with Elements upgrades — no per-app rewrite needed.
- Works in Next.js (App Router and Pages Router) and any React SPA.
Avoid the 404 / 500 / CSRF traps
These pages only work if the surrounding wiring is correct — most "the login
page is broken" reports are wiring, not the pages or the plugin. If you have not
run /project:ory-auth-setup, do that first; it establishes the four invariants these
pages depend on:
- First-party SDK URL — the browser must reach Ory on your own origin (the
Ory Tunnel or local gateway,
http://localhost:4000in dev), neverhttps://<slug>.projects.oryapis.comdirectly, or every form submit fails with a CSRF error. - Routes match the project config — the
/auth/*paths below must match the project's self-serviceui_urls and the middleware lists, and you must create an/auth/errorpage, or Ory's redirects 404. - Server calls forward cookies — server-side session/flow reads must forward
the request cookies (the
@ory/nextjsserver helpers do this); reusing the browser client on the server 500s.
See the Correctness contract and the App bug vs. plugin bug triage in
/project:ory-auth-setup for the full detail.
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 · 559 lines · 91 tokens per session scan A 755a88703c06
ory-login-flow is a skill published in the GitHub repository ory/claude-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 91 tokens to every session and 4,786 once invoked, about $0.0005 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…