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-rulesgit 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-rules)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-rules"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-rules/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-rules"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-rules.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.00166 | $0.01154 |
| Opus 5.5 | $0.00066 | $0.00462 |
| Sonnet 5.5 | $0.00033 | $0.00231 |
| Haiku 4.5 | $0.00017 | $0.00115 |
Grade A, and why
orchardcore-rules 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Rules
OrchardCore.Rules is the structured condition system used by features such as
Layers. A rule is a model of conditions evaluated against the current request
and context. It is different from OrchardCore.Scripting: scripting can power
a condition, but Rules provides condition models, editors, registration,
serialization, and composable all/any groups.
Guidelines
- Enable the exact
OrchardCore.Rulesfeature; it depends onOrchardCore.Scripting. - Use
Conditionas the base type for a custom condition. - Implement
IConditionEvaluatorwithValueTask<bool> EvaluateAsync(Condition condition). - Register standard conditions through
AddRuleCondition; do not use obsoleteAddCondition. - Use
AddRulewhen a condition has a display driver and the default condition factory is sufficient. - Register polymorphic JSON information through the provided registration extensions.
- Keep evaluators scoped because a rule can require request-scoped services or a scripting engine.
- Use a display driver to expose a condition in the rule builder UI.
- Do not treat a JavaScript condition as a substitute for structured authorization logic.
- All C# classes in examples are sealed except View Models.
Enable Rules
{
"steps": [
{
"name": "Feature",
"enable": [
"OrchardCore.Rules"
],
"disable": []
}
]
}
The module registers all, any, boolean, home page, URL, culture, role, JavaScript, authenticated, anonymous, and content-type conditions. It also registers string equality, prefix, suffix, and contains operators.
Core Types
| Type | Purpose |
|---|---|
Rule |
Serializable collection of conditions evaluated as a rule. |
Condition |
Base model with Name and ConditionId. |
ConditionGroup |
Base for nested groups such as all and any. |
IConditionEvaluator |
Evaluates a condition instance. |
IConditionFactory |
Creates a model for a builder condition. |
IConditionResolver |
Resolves evaluators for a condition. |
IConditionOperatorResolver |
Resolves configured string operators. |
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 · 149 lines · 166 tokens per session scan A 920d0f3cc779
orchardcore-rules is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 2d ago), licensed MIT. It adds 166 tokens to every session and 1,154 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
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.