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-notificationsgit 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-notifications)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-notifications"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-notifications/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-notifications"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-notifications.svg" alt="Reviewed on agentmods" width="80" 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.00158 | $0.01811 |
| Opus 5.5 | $0.00063 | $0.00724 |
| Sonnet 5.5 | $0.00032 | $0.00362 |
| Haiku 4.5 | $0.00016 | $0.00181 |
Grade A, and why
orchardcore-notifications 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 1mo 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Notifications - Prompt Templates
Create and Manage Notifications
Use INotificationService to create a persistent notification and dispatch it
through every delivery method available for the recipient. The service contract
is SendAsync(object notify, INotificationMessage message, CancellationToken);
it returns a NotificationSendResult.
Guidelines
- Enable
OrchardCore.Notificationsbefore using notification services. - Enable
OrchardCore.Notifications.Emailonly when email delivery is needed. - Send a
NotificationMessage, not aNotification; the service creates theNotificationentity. - Pass the recipient as the
notifyobject. Use application users when sending user notifications. - Inspect
NotificationSendResult.Status, counts, and errors when delivery outcomes affect application flow. - Implement
INotificationMethodProviderfor a delivery method. ItsSendAsyncreturnsTask<Result>. - Derive lifecycle handlers from
NotificationEventsHandler. - The module provides the
ManageNotificationspermission. Do not invent additional notification permissions. NotifyUserTaskandNotifyContentOwnerTaskare workflow activities registered when their required features are enabled.
Enabling Notifications
{
"steps": [
{
"name": "Feature",
"enable": [
"OrchardCore.Notifications",
"OrchardCore.Notifications.Email"
],
"disable": []
}
]
}
Notification and Message Models
NotificationMessage supplies the delivery content:
| Property | Purpose |
|---|---|
Subject |
Delivery subject, such as an email subject. |
Summary |
Short persistent notification summary. |
TextBody |
Plain-text body. |
HtmlBody |
HTML body when a provider supports it. |
IsHtmlPreferred |
Requests HTML when HtmlBody is available. |
The persisted Notification entity has NotificationId, Subject, Summary,
UserId, and CreatedUtc. The core event handler stores the message text and
HTML body as notification metadata.
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.
- 1mo ago First seen · 284 lines · 158 tokens per session scan A 0867143e2dd7
orchardcore-notifications is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 2d ago), licensed MIT. It adds 158 tokens to every session and 1,811 once invoked, about $0.0006 per session on Opus 5.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-12.
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…
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).
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
contentful-cms
Contentful content types, GraphQL/REST queries, CLI migrations, assets and locales. Use when changing a Contentful content model, querying Contentful, or migrating its content.
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.
sfcc-hooks-registration
Register SFCC hooks via cartridge package.json and hooks.json. Use when adding hooks or troubleshooting hook registration.