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-ai-workflowsgit 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-ai-workflows)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-ai-workflows"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-ai-workflows/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-ai-workflows"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-ai-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 30 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00204 | $0.02087 |
| Opus 5.5 | $0.00082 | $0.00835 |
| Sonnet 5.5 | $0.00041 | $0.00417 |
| Haiku 4.5 | $0.00020 | $0.00209 |
Grade A, and why
orchardcore-ai-workflows 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 4d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core AI Workflows
With OrchardCore.Workflows enabled, CrestApps AI Services adds two completion tasks and four chat session events.
Guidelines
- AI Completion using Profile needs
CrestApps.OrchardCore.AIandOrchardCore.Workflows. - AI Completion using Direct Config additionally needs
CrestApps.OrchardCore.AI.Chat.Interactions, because it reuses the chat interaction configuration model and completion pipeline. - The chat session events need an enabled chat feature (which brings
CrestApps.OrchardCore.AI.Chat.Core) plusOrchardCore.Workflows. Do not enableCrestApps.OrchardCore.AI.Chat.Coredirectly; enable a public chat feature such asCrestApps.OrchardCore.AI.Chat. - Both tasks render their prompt with Liquid, save a non-empty reply as an
AIResponseMessageinWorkflow.Output[ResultPropertyName](defaultChatResponse), and end on Done, Drew Blank, or Failed. - Prefix result names with
AI-to avoid collisions, and read the text with.Content. - Prefer the profile task in production so deployment, instructions, and capabilities are governed in one place.
- Install CrestApps packages in the web/startup project.
Enable
{
"steps": [
{
"name": "Feature",
"enable": [
"CrestApps.OrchardCore.AI",
"CrestApps.OrchardCore.AI.Chat",
"CrestApps.OrchardCore.AI.Chat.Interactions",
"OrchardCore.Workflows"
],
"disable": []
}
]
}
Drop CrestApps.OrchardCore.AI.Chat.Interactions if you only use the profile task, and CrestApps.OrchardCore.AI.Chat if you do not react to chat sessions.
AI Completion using Profile
- Create an AI profile with a chat deployment and the capabilities the workflow needs.
- Add AI Completion using Profile, select the profile, write a Liquid Prompt template, and set a Result Property Name such as
AI-order-summary. - Wire all three outcomes.
The template is rendered with the selected profile available as Profile. The task builds the completion context from the profile, resolves the chat deployment through the chat slot (IAIDeploymentManager.ResolveSlotAsync(AIDeploymentSlotNames.Chat, ...)), and sends the prompt as a user message.
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.
- 4d ago Changed · -26 lines · +36 tokens per session 0c7a9e4afef2
- 1mo ago First seen · 166 lines · 168 tokens per session scan A 5f43fa70ee09
orchardcore-ai-workflows is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 4d ago), licensed MIT. It adds 204 tokens to every session and 2,087 once invoked, about $0.0008 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-03.
Other skills, from other repositories
n8n-agents
Design n8n AI agents the right way. Use when building or editing any @n8n/n8n-nodes-langchain. AI node — an AI Agent, LLM chain, Text Classifier, or Information Extractor — and whenever the user mentions AI agents, LLM with tools, tool calling, $fromAI, system prompts, agent memory, sessionId, structured/JSON output…
coding-agents-prompt-authoring
To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
opik-optimize
Improve a prompt with the Opik Agent Optimizer — resolve the prompt, a dataset, and a metric, pick the algorithm, run a bounded optimization, check the gain on held-out data, and save the winner as a new prompt version with the optimization run link. Runs via the opik-optimizer package; reads prompts and datasets via…
strategy
Run structured brainstorming sessions (divergent/convergent), improve prompts with 7-dimension framework, and apply decision frameworks (RICE, weighted scoring, first principles, pre-mortem).
prompt-decorators-usage
Use when a user's prompt would clearly benefit from a reasoning, structure, tone, or verification decorator - or when they ask "what decorators should I use?". Teaches when and how to suggest inline ::Name(params) sigils instead of repeating verbose prompt-engineering instructions manually.
unified-ai-gateway
Operate and evaluate Unified AI System through fifteen governed MCP tools, including provider-free prompt enhancement, while preserving fake-provider, authorization, and evidence boundaries.