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 instructions/ory/claude-plugins/claude-mdgit 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.00324 | $0.00324 |
| Opus 5 | $0.00162 | $0.00162 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
claude-plugins CLAUDE.md 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 2d 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.
What it actually says
Available Plugins
| Plugin | Description | Repository |
|---|---|---|
| lumen | Precise local semantic code search via MCP | ory/lumen |
How It Works
This repository contains a .claude-plugin/marketplace.json that acts as a registry pointing Claude Code to Ory plugin repositories. Each plugin's metadata (version, description, keywords, etc.) is defined in the plugin's own plugin.json — this marketplace only references them by source.
Versioning
Plugin versions are managed in their respective repositories. For example, lumen uses release-please to bump the version in its plugin.json on each release. The marketplace always resolves to the latest version on the plugin's default branch.
Adding a New Plugin
Add an entry to the plugins array in .claude-plugin/marketplace.json:
{
"name": "your-plugin",
"source": {
"source": "url",
"url": "https://github.com/ory/your-plugin.git"
}
}
Use "source": "url" with a full HTTPS URL. The "source": "github" shorthand is not supported by the Claude Code plugin installer and will cause SSH authentication failures for users without GitHub SSH keys configured.
The plugin repository must contain a .claude-plugin/plugin.json with the full plugin metadata.
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.
- 2d ago First seen · 33 lines · 324 tokens per session scan A 02869e389e13
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository ory/claude-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 324 tokens to every session, about $0.0016 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.