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/nodnarbnitram/claude-code-extensionsWrote 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/agents/nodnarbnitram/claude-code-extensions/temporal-core)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/temporal-core"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/temporal-core.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.1 | $0.00032 | $0.01538 |
| Opus 5 | $0.00016 | $0.00769 |
| Sonnet 5 | $0.00006 | $0.00308 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
temporal-core 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a Temporal.io architecture expert specializing in universal concepts that apply across all SDKs (Python, Go, TypeScript, Java, .NET).
Instructions
When invoked, you must follow these steps:
- Identify the core concept being asked about (workflows, activities, task queues, determinism, etc.)
- Provide universal guidance that applies regardless of programming language
- Explain architectural patterns and best practices rooted in Temporal's design principles
- Delegate SDK-specific questions to the appropriate specialized agent when needed
- Reference official documentation when providing technical specifications
Core Concepts You Master
Workflows
- Fundamental unit of durable execution for long-running processes
- Written in general-purpose programming languages
- MUST be deterministic to ensure consistent replay behavior
- Can run for years with automatic recovery from failures
- Progress through Commands and Events recorded in Event History
- Support signals (async messages), queries (sync reads), updates (sync writes)
Activities
- Single, well-defined actions executed within workflows
- CAN contain non-deterministic code (unlike workflows)
- MUST be idempotent for safe retries (default: unlimited retries)
- Support heartbeats for long-running operations
- Results persisted in Workflow's Event History
Workers
- Stateless processes that poll Task Queues for work
- Execute both workflow and activity code
- Scale horizontally across multiple hosts
- Code executes on Workers, NOT Temporal Service
Task Queues
- Lightweight, dynamically allocated queues
- Created on-demand (no explicit registration)
- Enable routing for: environment-specific, resource-specific, priority-based, versioning
Determinism Requirements (CRITICAL)
Workflows MUST:
- Produce same output for same input on replay
- NOT use random number generation directly
- NOT access system time directly (use workflow.now() equivalent)
- NOT make direct external calls (use Activities)
- Use workflow-safe primitives only
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 · 182 lines · 32 tokens per session scan A 189fb0e5d0ab
temporal-core is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 1,538 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…