duroxide copilot-instructions.md

Project instructions for Duroxide, a Rust runtime that runs workflows reliably across queues, timers, external events, and long-running tasks.

In plain words
What is it for?
Use them when developing or testing Duroxide orchestration, worker activities, durable timers, waiting, sub-workflows, and related Rust code.
Why use it?
They keep an agent aligned with the project's architecture and testing rules, including the required test runner and restrictions on Git operations.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/affandar/duroxide/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/affandar/duroxide

Made for: GitHub Copilot.

Per session 1,874 This file is loaded in full into every session.
When invoked 1,874 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01874 $0.01874
Opus 5 $0.00937 $0.00937
Sonnet 5 $0.00375 $0.00375
Haiku 4.5 $0.00187 $0.00187

Measured 2d ago against content hash 8d5781b11b62, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

duroxide copilot-instructions.md 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.

.github/copilot-instructions.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Duroxide AI Agent Instructions

A durable execution runtime for Rust. Key docs: docs/ORCHESTRATION-GUIDE.md, docs/provider-implementation-guide.md.

⚠️ CRITICAL: Git Operations

NEVER commit or push without explicit user permission. Always ask before running git commit or git push.

⚠️ CRITICAL: Test Execution

ALWAYS use nextest for running tests. This is mandatory - nextest provides faster execution and better output.

cargo nt                              # Run all tests (nextest alias)
cargo nt -E 'test(/pattern/)'         # Filter tests by pattern
cargo nt --test specific_test_file    # Run specific test file

Only fall back to cargo test if nextest is not available. Never use cargo test when cargo nt works.

Architecture Overview

Two-queue message-driven runtime:

  • OrchestrationDispatcher (orchestrator queue): Processes workflow turns, durable timers, and external events
  • WorkDispatcher (worker queue): Executes activities with automatic lock renewal for long-running work

Core types:

  • OrchestrationContext - Schedules work via schedule_activity(), schedule_timer(), schedule_wait(), schedule_sub_orchestration() - all return futures you can .await directly
  • Event/Action - Immutable history entries; providers only store, never generate IDs
  • Provider trait - Storage abstraction with peek-lock semantics (src/providers/mod.rs)

Critical Patterns

Awaiting schedule_ methods:*

// schedule_* methods return futures that can be awaited directly
let result = ctx.schedule_activity("Task", input).await?;
ctx.schedule_timer(Duration::from_secs(5)).await;
let event_data = ctx.schedule_wait("MyEvent").await;
let sub_result = ctx.schedule_sub_orchestration("Child", input).await?;

Use ctx.join/select, NOT tokio::join/select:

// ✅ CORRECT - deterministic, history-ordered resolution
match ctx.select2(timer, activity).await {
    Either2::First(()) => { /* timer won */ }
    Either2::Second(result) => { /* activity won */ }
}
let results = ctx.join(vec![f1, f2, f3]).await;

// ❌ WRONG - non-deterministic, breaks replay
let (a, b) = tokio::join!(f1, f2);  // NEVER use tokio::join in orchestrations!
tokio::select! { ... }              // NEVER use tokio::select in orchestrations!

Read the full file on GitHub · 169 lines

Changes

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.

  1. 2d ago First seen · 169 lines · 1,874 tokens per session scan A 8d5781b11b62

Subscribe to this mod's changes

duroxide copilot-instructions.md is an instructions file published in the GitHub repository affandar/duroxide (20 stars, last pushed 6mo ago), licensed MIT. It adds 1,874 tokens to every session, about $0.0094 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.