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 instructions/lucaslorentz/durabletask-extensions/claude-mdgit clone --depth 1 https://github.com/lucaslorentz/durabletask-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/instructions/lucaslorentz/durabletask-extensions/claude-md)<a href="https://agentmods.dev/instructions/lucaslorentz/durabletask-extensions/claude-md"><img src="https://agentmods.dev/badge/instructions/lucaslorentz/durabletask-extensions/claude-md.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 | $0.00682 | $0.00682 |
| Opus 5 | $0.00341 | $0.00341 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
durabletask-extensions CLAUDE.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 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Instructions
Language
English for everything: code, commits, PR titles/bodies, issue/PR comments, and docs.
Project Overview
This is a .NET library (NuGet packages) extending Azure Durable Task Framework. Multi-target: net10.0, net9.0, net8.0. Frontend: React 18 + MUI 5 + TypeScript + Vite.
Development Workflow
Before every commit, follow this sequence:
1. Build
dotnet build
Must pass with 0 warnings and 0 errors.
2. Unit Tests
dotnet test --filter "FullyQualifiedName~InMemory" --no-build
InMemory tests run without Docker. All 3 TFMs (net10.0, net9.0, net8.0) must pass.
3. UI Smoke Test via Aspire
Start all services at once using the Aspire AppHost:
dotnet run --project samples/AppHost/AppHost.csproj
This starts: Server, Api, Ui, OrchestrationWorker, CarWorker, FlightWorker, HotelWorker, BpmnWorker.
Then use Playwright to verify the UI:
- Navigate to the UI (https://localhost:5002)
- Verify the home page loads ("Welcome to Durable Task UI")
- Navigate to Orchestrations page - verify table renders
- Create a BookParallel orchestration (Name:
BookParallel, Version:v1, Input:{}) - Wait a few seconds for workers to process it
- Refresh and verify Status changes to Completed
- Check the History tab - verify the full execution flow is visible
- Take screenshots as evidence
After verification, stop the Aspire process.
4. Commit
Only commit after all steps above pass successfully.
Package Versioning Rules
Since src/ projects are published NuGet libraries:
- Microsoft.Extensions.* and Microsoft.EntityFrameworkCore.* must stay at the minimum compatible version for each TFM (e.g., 10.0.0 not 10.0.3 for net10.0). This maximizes compatibility for consumers.
- Non-framework packages (DurableTask.Core, gRPC, Protobuf, SourceLink, etc.) should be updated to latest stable versions.
- Test, sample, and benchmark projects (not published) can use latest versions freely.
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 · 92 lines · 682 tokens per session scan A 33bebd5bf68c
durabletask-extensions CLAUDE.md is an instructions file published in the GitHub repository lucaslorentz/durabletask-extensions (67 stars, last pushed 3d ago), licensed MIT. It adds 682 tokens to every session, about $0.0034 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-01.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.