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 commands/ory/claude-plugins/local-upgit 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.00000 | $0.00207 |
| Opus 5 | $0.00000 | $0.00103 |
| Sonnet 5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
local-up 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
Start Local Ory Environment
Start the local Ory development environment using Docker Compose. This spins up Kratos (identity), Keto (permissions), Hydra (OAuth2), and an Nginx gateway on port 4000.
Run:
npx -y -p @ory/claude-code ory-claude local up
This will:
- Start all Ory services in Docker containers
- Wait for the gateway to become healthy
- Seed test data (identity, session, and permission tuples)
- Print environment variables to connect
After it completes, set the printed environment variables in your shell:
eval "$(npx -y -p @ory/claude-code ory-claude local env)"
If services are already running, stop them first with /ory-agent-plugin:local-down
or use npx -y -p @ory/claude-code ory-claude local status to check the current state.
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 · 28 lines · 0 tokens per session scan A bb595fd965b0
local-up is a command published in the GitHub repository ory/claude-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 207 tokens. 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 commands, from other repositories
sandbox
Manage sandbox backends and tooling.
polyphony-init
Initialize the Polyphony multi-agent orchestration environment.
dockerfile
Validate Dockerfiles for GPU/CUDA configuration issues before building.
index
Command "index" from thrashr888/agentkernel, covering commands, quick reference, daily drivers (root level), sandbox lifecycle (sandbox / sb) and ssh (ssh).
images
Manage Docker images and build custom images from Dockerfiles.
snapshots
Save and restore sandbox state. Snapshots capture the full filesystem of a running or stopped sandbox using docker commit.