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-layersgit 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-layers)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-layers"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-layers/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-layers"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-layers.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.00171 | $0.01800 |
| Opus 5.5 | $0.00068 | $0.00720 |
| Sonnet 5.5 | $0.00034 | $0.00360 |
| Haiku 4.5 | $0.00017 | $0.00180 |
Grade A, and why
orchardcore-layers 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Layers - Prompt Templates
Configuring Layers for Conditional Widget Display
You are an Orchard Core expert. Generate configuration and code for managing layers and conditional widget visibility in Orchard Core.
Guidelines
- Layers are provided by the
OrchardCore.Layersmodule and control when widgets are displayed in theme zones. - A Layer has a name, description, and one or more conditions (rules) that determine when its widgets are visible.
- Widgets placed in a zone must be associated with a Layer; the widget renders only when the Layer's rules evaluate to
true. - Layers are managed from Design > Widgets in the admin panel.
- Available zones are configured in Design > Settings > Zones and must match theme layout sections.
- Conditions can be combined using
All(AND) andAny(OR) condition groups. - The
Alwayslayer uses aBooleancondition set totrue, so widgets on this layer always render. - Enable
OrchardCore.LayersandOrchardCore.Widgetsfeatures for full widget/layer support. - Always wrap recipe JSON in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier except View Models. - Use file-scoped namespaces in C# examples.
Enabling Layer Features
{
"steps": [
{
"name": "Feature",
"enable": [
"OrchardCore.Layers",
"OrchardCore.Widgets"
],
"disable": []
}
]
}
Available Conditions
| Condition | Description |
|---|---|
Homepage |
True when the current page is the site homepage |
Is anonymous |
True when the current user is not authenticated |
Is authenticated |
True when the current user is authenticated |
Role |
Evaluates the current user's roles against a value |
Url |
Evaluates the current URL against a value |
Culture |
Evaluates the current UI culture against a value |
Content Type |
Evaluates the currently displayed content type against a value |
Javascript |
A custom script condition written in JavaScript |
All |
Condition group where all nested conditions must be true (AND logic) |
Any |
Condition group where at least one nested condition must be true (OR logic) |
Boolean |
A simple true/false condition |
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 · 240 lines · 171 tokens per session scan A 3216f41d7b2e
orchardcore-layers is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 2d ago), licensed MIT. It adds 171 tokens to every session and 1,800 once invoked, about $0.0007 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
powerpoint-mcp
Use the configured PowerPoint MCP server to inspect or edit presentations on Windows. Covers session safety, live tool discovery, saving, and visual verification; not general presentation design. Triggers: PowerPoint MCP, presentation tools, edit a PowerPoint deck.
powerpoint-cli
Discover and use the PowerPoint CLI plugin to automate a live PowerPoint desktop session. Use for terminal, PowerShell, batch, and coding-agent tasks; not general presentation design. Triggers: pptcli, PowerPoint command line, presentation automation script.
powerpoint-deck-design
Plan or improve the visual design of a PowerPoint presentation: layout, typography, color, hierarchy, accessibility, and consistency. Use when the user asks to create, redesign, or review how a deck looks; not for general PowerPoint automation or content-only edits.
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
release-notes
Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.
home-memory-documentation
Do not load unless the request or established context explicitly identifies Home Memory (HM) and requires a documentation decision about record boundaries, relationships or information placement. If the product is ambiguous, ask whether the user means Home Memory or Smartconstruct and load neither product skill first.…