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.
git 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/commands/ory/claude-plugins/temporal-up)<a href="https://agentmods.dev/commands/ory/claude-plugins/temporal-up"><img src="https://agentmods.dev/badge/commands/ory/claude-plugins/temporal-up/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ory/claude-plugins/temporal-up"><img src="https://agentmods.dev/badge/commands/ory/claude-plugins/temporal-up.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00380 |
| Opus 5.5 | $0.00000 | $0.00152 |
| Sonnet 5.5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
temporal-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 1mo 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 Temporal Dev Server
Start a local Temporal development server alongside the
local Ory stack so the worker scaffolded by ory-temporal-worker can connect.
This runs Temporal's bundled dev server (Temporal Server + Postgres + Web UI in
one process) — not a production cluster.
Prerequisite: the Temporal CLI is installed and
temporal is on PATH. On macOS: brew install temporal. On Linux/Windows:
download from https://temporal.download.
Run:
temporal server start-dev
This will:
- Start the Temporal Server on
localhost:7233(the gRPC endpoint workers and clients connect to) - Expose the Web UI on http://localhost:8233
- Persist state under
~/.config/temporalio/so workflows survive a restart
The process runs in the foreground. Stop it with Ctrl+C; data is preserved.
For a clean reset, delete ~/.config/temporalio/ and start again.
For the matching Ory side of the stack (Identities, Permissions, OAuth2, login
UI), use /ory-agent-plugin:local-up. The two stacks are independent — Temporal
runs on :7233/:8233, Ory runs on :4000 and friends — so they can run side
by side without port conflicts.
Once both are up, point the worker at them:
export ORY_PROJECT_URL=http://localhost:4000
export ORY_AUTH_GATE=1
cd temporal-worker
npm run start
See the ory-temporal-worker skill for the full worker scaffold and the
permission-gate wiring.
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.
- 1mo ago First seen · 44 lines · 0 tokens per session scan A c8876c7f3958
temporal-up is a command published in the GitHub repository ory/claude-plugins (3 stars, last pushed 17d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 380 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.