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/proyecto26/projectx/temporalnpx skills add proyecto26/projectx --skill temporalgit clone --depth 1 https://github.com/proyecto26/projectxWhat 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.00161 | $0.02187 |
| Opus 5 | $0.00081 | $0.01094 |
| Sonnet 5 | $0.00032 | $0.00437 |
| Haiku 4.5 | $0.00016 | $0.00219 |
Grade A, and why
temporal 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.
How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Temporal Workflow Development
Overview
Temporal is a durable execution platform that makes workflows survive failures automatically. This skill provides guidance for building Temporal applications.
Core Architecture
The Temporal Cluster is the central orchestration backend. It maintains three key subsystems: the Event History (a durable log of all workflow state), Task Queues (which route work to the right workers), and a Visibility store (for searching and listing workflows). There are three ways to run a Cluster:
- Temporal CLI dev server — a local, single-process server started with
temporal server start-dev. Suitable for development and testing only, not production. - Self-hosted — you deploy and manage the Temporal server and its dependencies (e.g., database) in your own infrastructure for production use.
- Temporal Cloud — a fully managed production service operated by Temporal. No cluster infrastructure to manage.
Workers are long-running processes that you run and manage. They poll Task Queues for work and execute your code. You might run a single Worker process on one machine during development, or run many Worker processes across a large fleet of machines in production. Each Worker hosts two types of code:
- Workflow Definitions — durable, deterministic functions that orchestrate work. These must not have side effects.
- Activity Implementations — non-deterministic operations (API calls, file I/O, etc.) that can fail and be retried.
Workers communicate with the Cluster via a poll/complete loop: they poll a Task Queue for tasks, execute the corresponding Workflow or Activity code, and report results back.
History Replay: Why Determinism Matters
Temporal achieves durability through history replay:
- Initial Execution - Worker runs workflow, generates Commands, stored as Events in history
- Recovery - On restart/failure, Worker re-executes workflow from beginning
- Matching - SDK compares generated Commands against stored Events
- Restoration - Uses stored Activity results instead of re-executing
What ships with it
20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/core/ai-patterns.md 5.5 KB
- references/core/determinism.md 5.6 KB
- references/core/dev-management.md 1009 B
- references/core/error-reference.md 3.0 KB
- references/core/gotchas.md 7.9 KB
- references/core/interactive-workflows.md 1.3 KB
- references/core/patterns.md 15 KB
- references/core/troubleshooting.md 9.3 KB
- references/core/versioning.md 5.1 KB
- references/typescript/advanced-features.md 4.0 KB
- references/typescript/data-handling.md 5.9 KB
- references/typescript/determinism-protection.md 2.4 KB
- references/typescript/determinism.md 2.0 KB
- references/typescript/error-handling.md 3.3 KB
- references/typescript/gotchas.md 9.1 KB
- references/typescript/observability.md 3.2 KB
- references/typescript/patterns.md 11 KB
- references/typescript/testing.md 6.1 KB
- references/typescript/typescript.md 6.4 KB
- references/typescript/versioning.md 6.9 KB
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 · 251 lines · 161 tokens per session scan A b703751f146e
temporal is a skill published in the GitHub repository proyecto26/projectx (83 stars, last pushed 4mo ago), licensed MIT. It adds 161 tokens to every session and 2,187 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-30.
Other skills, from other repositories
hex-release
Guides interactive Hex package release for AgentJido repos. Supports automated (GitHub Actions workflowdispatch) and manual release flows. Uses gitops for version bumping and changelog generation. Triggers on: release, hex publish, bump version, new release, publish package.
getting-started
Get started with your Open SaaS project — fetches docs, checks Wasp installation, and helps you start your database and app.
guided-tour
Take a guided tour of Open SaaS — walks you through step-by-step through the project structure, features, and customization checklist.
add-wasp-skills
Install Wasp agent skills (plugins) that add Wasp knowledge and best practices to your AI coding tools.
pr-review
Review a Pull Request for code quality, tests, merge conflicts, and readiness to merge.
cabloy-spec-generation
This skill should be used for requests to create or maintain a Cabloy repo-specs/ / set, including a PRD, SRS, PDP/WBS, test plan, progress register, suite ADR, or “write the specs”/“plan the suite.” It links product, technical, delivery, acceptance, and decision records after the domain boundary is confirmed. Route…