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-temporal-workernpx skills add ory/claude-plugins --skill ory-temporal-workergit 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-temporal-worker)<a href="https://agentmods.dev/skills/ory/claude-plugins/ory-temporal-worker"><img src="https://agentmods.dev/badge/skills/ory/claude-plugins/ory-temporal-worker.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.00155 | $0.02473 |
| Opus 5 | $0.00077 | $0.01236 |
| Sonnet 5 | $0.00031 | $0.00495 |
| Haiku 4.5 | $0.00015 | $0.00247 |
Grade A, and why
ory-temporal-worker 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ory-authed Temporal TypeScript worker
You are helping the user scaffold a Temporal TypeScript worker where every Activity execution is gated by Ory: the user is authenticated, the worker's agent identity is resolved via OAuth2 Dynamic Client Registration, each Activity invocation runs an Ory Permission check, and the full lifecycle emits structured activity events. Workflows stay deterministic — only Activities call out to Ory.
This skill carries the workflow. You generate the files in the user's repo; the user runs the Temporal CLI and the worker.
Precondition: Node.js 20+ is installed, and the user has installed (or will install) the Temporal CLI. On macOS:
brew install temporal. On Linux/Windows: download from https://temporal.download and puttemporalonPATH. If the binary is missing, point the user at the docs and stop — do not fabricate it.
Step 1 — Confirm the target
Before writing files, confirm with the user:
- Where the worker should live. Default to
temporal-worker/at the repo root unless the user says otherwise. - Task queue name. Default
agent-tools. The worker and the workflow starter must agree on this string. - Ory project URL. For local development point at the local Ory stack
(
/ory-agent-plugin:local-up) onhttp://localhost:4000. For Ory Network, the user plumbs their project URL through the worker's env. Either way the worker needs network reachability to the Ory APIs at runtime.
Step 2 — Scaffold the Temporal project
Run the official Temporal scaffold and select the hello-world sample when
prompted. Then add the Ory agent client:
npx @temporalio/create@latest temporal-worker
cd temporal-worker
npm install @ory/argus
The scaffold lays down src/{activities.ts, workflows.ts, worker.ts, client.ts}
and pre-configures the Worker to connect to the Temporal dev server at
localhost:7233. The Web UI lives at http://localhost:8233 once the dev
server is running.
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 · 282 lines · 155 tokens per session scan A a9fa5b351e8f
ory-temporal-worker is a skill published in the GitHub repository ory/claude-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 155 tokens to every session and 2,473 once invoked, about $0.0008 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 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…