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 skills add CrestApps/CrestApps.AgentSkills --skill orchardcore-deferred-tasksgit clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkillsWrote 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/crestapps/crestapps.agentskills/orchardcore-deferred-tasks)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-deferred-tasks"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-deferred-tasks.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00189 | $0.01416 |
| Opus 5 | $0.00095 | $0.00708 |
| Sonnet 5 | $0.00038 | $0.00283 |
| Haiku 4.5 | $0.00019 | $0.00142 |
Grade A, and why
orchardcore-deferred-tasks 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Deferred Tasks and After-Request Background Jobs
Orchard Core provides two complementary ways to run code after the main work
of a request, without adding a scheduled IBackgroundTask. Both live in the
OrchardCore.Abstractions package, so any module can use them.
ShellScope.AddDeferredTask— runs a delegate in a fresh isolated scope once the current shell scope tears down, after the YesSql session has been committed. Use it to react to committed data (indexing, cache busting, sending a signal) and to see your own just-saved changes.HttpBackgroundJob.ExecuteAfterEndOfRequestAsync— truly fire-and-forget. It returns immediately, waits for the currentHttpContextto be released (end of the HTTP response), reloads the shell, restores the current user, and runs the job in an isolated scope. Use it for longer work you do not want the client to wait for.
When to use which
| Need | Use |
|---|---|
| Run right after commit, still part of request teardown, client waits | ShellScope.AddDeferredTask |
| Run after the response is sent, do not block the client | HttpBackgroundJob.ExecuteAfterEndOfRequestAsync |
| Only send an invalidation signal after commit | ShellScope.AddDeferredSignal |
| Run something as the scope disposes (no new scope) | ShellScope.RegisterBeforeDispose |
Why "after the session is saved" works
The YesSql/document session commit is registered as a before-dispose callback on the shell scope. During scope teardown Orchard Core runs, in order:
RegisterBeforeDisposecallbacks — this is whereIDocumentStore.CommitAsync()commits the session.- Deferred signals added via
AddDeferredSignal. - Deferred tasks added via
AddDeferredTask, each in its own new scope (with a fresh session) built from the reloaded shell.
Because the commit happens in step 1 and deferred tasks run in step 3, a deferred task always observes committed data and never fights the request's open transaction. Kicking off the background job from inside a deferred task guarantees the job is only scheduled after a successful commit.
What ships with it
1 file 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.
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 · 133 lines · 189 tokens per session scan A a6a2f4b0a86e
orchardcore-deferred-tasks is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 10d ago), licensed MIT. It adds 189 tokens to every session and 1,416 once invoked, about $0.0009 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 skills, from other repositories
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration, hosting, or deployment behavior; deciding…
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
clean-architecture-dotnet
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
csharp-expert
Expert-level C# development with .NET 8+, ASP.NET Core, LINQ, async/await, and enterprise patterns. Use when the user mentions C#, .NET, ASP.NET, enterprise, or Microsoft platforms, or when the task involves Modern C#, Async/Await, LINQ, or ASP.NET Core.
sfcc-job-development
Guide for developing custom jobs in Salesforce B2C Commerce Job Framework. Use this when asked to create batch jobs, scheduled tasks, chunk-oriented processing, or task-oriented jobs.