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/roedyrustam/vibes-plug/async-queue-temporal-expertnpx skills add roedyrustam/vibes-plug --skill async-queue-temporal-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/async-queue-temporal-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/async-queue-temporal-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/async-queue-temporal-expert.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.00062 | $0.00844 |
| Opus 5 | $0.00031 | $0.00422 |
| Sonnet 5 | $0.00012 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
async-queue-temporal-expert 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 5d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Async Queue & Durable Workflow Expert
English
Purpose & Overview
Production-grade guidance for designing durable, fault-tolerant background execution pipelines and distributed state machines using Temporal.io, Trigger.dev v3, Inngest, and BullMQ v5. Guarantees execution completion across long-running background tasks, API rate limits, and server crashes.
Key Capabilities
- Durable Execution: Automatic retry, state persistence, and resume after server restarts or network partitions.
- Saga Pattern Orchestration: Multi-step distributed transactions with compensation logic for rollback on failure.
- Rate Limiting & Concurrency: Controlled worker concurrency, backoff jitter, and per-tenant queue isolation.
import { task } from "@trigger.dev/sdk/v3";
export const generateSaaSReport = task({
id: "generate-saas-report",
run: async (payload: { tenantId: string }) => {
// Durable step execution with automatic retries
const data = await fetchTenantData(payload.tenantId);
const pdfUrl = await generatePDF(data);
await sendEmailReport(payload.tenantId, pdfUrl);
return { success: true, pdfUrl };
},
});
Implementation Checklist
- Define background tasks idempotently so they can be safely retried without side effects.
- Offload heavy payloads to cloud storage (S3) and pass only reference IDs/URLs through the queue.
- Configure concurrency limits per tenant/worker to avoid rate limit bans from third-party APIs.
- Implement compensation tasks (rollback) for distributed saga patterns if a downstream step fails permanently.
Bahasa Indonesia
Integrasi Orkestrasi
Terhubung dan mengorkestrasi skill domain yang relevan seperti brainstorming, zero-to-prod-orchestrator, dan project-context-mapper untuk memastikan eksekusi yang kohesif.
Deskripsi
Panduan tingkat produksi untuk merancang pipeline eksekusi background yang tahan-gagal (durable execution) dan state machine terdistribusi menggunakan Temporal.io, Trigger.dev v3, Inngest, dan BullMQ v5. Menjamin penyelesaian eksekusi tugas background berdurasi panjang meskipun terjadi server crash atau pembatasan API rate limit.
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.
- 5d ago First seen · 70 lines · 62 tokens per session scan A 502a04cd0d8b
async-queue-temporal-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (49 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 844 once invoked, about $0.0003 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
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
test-driven-development
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
documentation-and-adrs
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
incremental-implementation
Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
source-driven-development
Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.