Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkillsnpx agentmods add skills/crestapps/crestapps.agentskills/orchardcore-modulesWrote 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-modules)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-modules"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-modules/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-modules"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-modules.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.00159 | $0.00966 |
| Opus 5.5 | $0.00064 | $0.00386 |
| Sonnet 5.5 | $0.00032 | $0.00193 |
| Haiku 4.5 | $0.00016 | $0.00097 |
Grade A, and why
orchardcore-modules 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Modules - Prompt Templates
Create a Module
You are an Orchard Core expert. Generate the scaffolding for a module owned by
an application that consumes Orchard Core packages. For a contribution inside
the Orchard Core source repository, use the orchardcore-module-creator
skill instead.
Guidelines
- Module names should be PascalCase and typically prefixed with the organization name (e.g.,
MyOrg.MyModule). - Every module must have a
Manifest.csfile declaring its features. - Each feature must have a unique ID and should declare its dependencies.
- Use
Startupclasses to register services, routes, and navigation. - Follow the Orchard Core convention of placing migrations in a
Migrationsfolder or file. - Declare a new feature with
[assembly: Feature(...)]only when the user should manage it; to extend or override behavior when other features are present, gate aStartupwith[RequireFeatures(...)]instead of adding another feature the user must enable. See theorchardcore-featuresskill for the full decision. - Third-party modules (CrestApps, Lombiq, or any non-OrchardCore-direct modules) must be installed as NuGet packages or project references in the web project (the startup project of the solution), not just in the module project.
- Always seal classes.
Installing Third-Party Modules
Third-party modules are installed by adding NuGet packages or project references to the web project:
<Project Sdk="Microsoft.NET.Sdk.Web">
<ItemGroup>
<!-- Orchard Core base -->
<PackageReference Include="OrchardCore.Application.Cms.Targets" Version="3.*" />
<!-- Third-party modules must be in the web project -->
<PackageReference Include="Lombiq.HelpfulExtensions.OrchardCore" Version="1.*" />
</ItemGroup>
</Project>
For local module projects:
<ItemGroup>
<ProjectReference Include="../ThirdParty.Module/ThirdParty.Module.csproj" />
</ItemGroup>
Manifest Pattern
using OrchardCore.Modules.Manifest;
[assembly: Module(
Name = "{{ModuleName}}",
Author = "{{Author}}",
Website = "{{Website}}",
Version = "1.0.0",
Description = "{{Description}}",
Category = "{{Category}}"
)]
[assembly: Feature(
Id = "{{ModuleName}}",
Name = "{{FeatureName}}",
Description = "{{FeatureDescription}}",
Dependencies = new[]
{
"OrchardCore.ContentManagement"
},
Category = "{{Category}}"
)]
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 · 132 lines · 159 tokens per session scan A 6dd4c32ee247
orchardcore-modules is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 2d ago), licensed MIT. It adds 159 tokens to every session and 966 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.