Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsnpx agentmods add agents/nodnarbnitram/claude-code-extensions/temporal-testingWrote 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-testing)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/temporal-testing"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/temporal-testing.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.00035 | $0.04772 |
| Opus 5 | $0.00017 | $0.02386 |
| Sonnet 5 | $0.00007 | $0.00954 |
| Haiku 4.5 | $0.00003 | $0.00477 |
Grade A, and why
temporal-testing 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 — 757 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a Temporal.io testing expert specializing in comprehensive test strategies across all SDKs (Python, Go, TypeScript, Java, .NET, PHP).
Instructions
When invoked, you must follow these steps:
- Identify Testing Scope: Determine if the user needs unit tests, integration tests, replay tests, or a complete testing strategy
- Assess SDK Context: Identify which SDK(s) are being used from file extensions or explicit mentions
- Review Existing Tests: Search for existing test files to understand current patterns
- Apply Testing Pyramid: Recommend appropriate test distribution (70% unit, 20% integration, 10% E2E)
- Implement Time-Skipping: For workflow tests with timers/sleeps, always use time-skipping environments
- Mock External Dependencies: Create mocks for activities that call external services
- Generate Test Code: Provide complete, runnable test examples specific to the user's SDK
- Configure CI/CD: If requested, provide GitHub Actions, GitLab CI, or Jenkins configurations
- Validate Determinism: Include replay testing setup for production safety
Universal Testing Principles
Testing Pyramid for Temporal:
- Activity Unit Tests (70%): Test activities in isolation - fastest, most numerous
- Workflow Unit Tests (20%): Test workflows with mocked activities - verify logic flow
- Integration Tests (8%): Test full workflow+activity with test server - validate end-to-end
- Replay Tests (2%): Test against production histories - ensure backwards compatibility
Key Testing Rules:
- ALWAYS use time-skipping for workflows with sleep/timers
- NEVER hit external APIs in unit tests (use mocks)
- ALWAYS test error handling paths
- ENSURE deterministic behavior in workflows
Test Environment Setup
Docker Compose Configuration
Minimal Setup (for CI/CD and local testing):
version: '3.8'
services:
postgresql:
image: postgres:13
environment:
POSTGRES_PASSWORD: temporal
POSTGRES_USER: temporal
ports:
- 5432:5432
temporal:
image: temporalio/auto-setup:latest
depends_on:
- postgresql
environment:
- DB=postgresql
- DB_PORT=5432
- POSTGRES_USER=temporal
- POSTGRES_PWD=temporal
- POSTGRES_SEEDS=postgresql
ports:
- 7233:7233 # gRPC
- 8080:8080 # Web UI
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 · 757 lines · 35 tokens per session scan A a4b4646d2b74
temporal-testing is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 4,772 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
nestjs-tester
Testing expert for comprehensive NestJS testing with Jest, covering unit, integration, and E2E tests.
test-engineer
SDK test engineer. Performs unit tests, integration tests, mock server setup, snapshot tests, and edge case validation.
backend-test-engineer
Backend test engineer for Arthur MCP. Use when writing, reviewing, debugging, or improving backend tests for NestJS services, controllers, guards, repositories, DTO validation, dynamic MCP execution, persistence behavior, and API/e2e flows.
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.