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-toolsgit 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-tools)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-ai-tools"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-ai-tools.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00185 | $0.01858 |
| Opus 5 | $0.00093 | $0.00929 |
| Sonnet 5 | $0.00037 | $0.00372 |
| Haiku 4.5 | $0.00018 | $0.00186 |
Grade A, and why
orchardcore-ai-tools 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 5d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core AI Tools - Prompt Templates
Register and Select AI Tools
You are an Orchard Core expert. Generate secure AI tool registration and selection patterns for CrestApps AI Services. A tool is a named AITool registered in the shared Core tool definitions and resolved as a keyed service when an authorized completion needs it.
Guidelines
- Enable
CrestApps.OrchardCore.AIfor the Orchard Core AI tool selection and permission integration. - Register a tool through
AddCoreAITool<TTool>(name)and give it a unique, stable name. AddCoreAIToolregisters the keyedAIToolservice and its definition under the same name. Do not register an unrelated duplicate keyed service.- A new Core tool is hidden by default. Call
.Selectable()only when Orchard users should be able to select it. - Set title, description, and category with the returned builder; these values drive capability pickers.
GetSelectableTools()excludes tools marked as system tools. System tools are for internal orchestration paths and are not shown in capability pickers.LocalToolRegistryProviderreturns only names configured on the completion context, skips system tools, and checksAccessAIToolauthorization.- The provider resolves a selected tool from DI with
GetKeyedService<AITool>(toolName). - Tool selection is stored as
FunctionInvocationMetadata.Namesfor AI Profiles. - Profile-source templates store selected names in
ProfileTemplateMetadata.ToolNames. - Chat Interactions store selected names in
ChatInteraction.ToolNames. - Direct-config workflow tasks store selected names in
AICompletionWithConfigTask.ToolNames. - Capability editors group tools by category and filter them by the current editor's permission.
- The
AccessAnyAIToolpermission is security-critical. DynamicAccessAITool_{toolName}permissions are created for registered definitions. - Do not make privileged system-management, content-management, or external side-effect tools available by default.
- Tool metadata must accurately describe side effects, required access, and argument expectations so orchestration can select safely.
- Install CrestApps packages in the web/startup project.
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.
- 5d ago First seen · 183 lines · 185 tokens per session scan A f869e8bb1ba0
orchardcore-ai-tools is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 10d ago), licensed MIT. It adds 185 tokens to every session and 1,858 once invoked, about $0.0009 per session on Opus 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
powerpoint-cli
PowerPoint CLI automation skill for Windows presentations. Use when a coding agent needs token-efficient, scriptable, or unattended PowerPoint automation via pptcli commands. Best for CI/CD, scheduled jobs, batch processing, PowerShell workflows, and bulk deck edits. Supports slides, shapes, text frames, tables…
powerpoint-mcp
PowerPoint MCP Server skill for Windows presentation automation via a live PowerPoint desktop instance (COM/PIA). Use when an assistant needs rich MCP tools to create, open, build, format, and export PowerPoint (.pptx/.pptm) presentations — slides, shapes, text boxes, tables, native charts, images, audio, video…
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.
dotnet-debugging
Debug .NET applications using debug-mcp MCP tools — launch processes, set breakpoints, step through code, inspect variables, evaluate expressions, and analyze exceptions. Use this skill when debugging .NET/C# applications, investigating runtime behavior, diagnosing exceptions, inspecting object state, or performing…
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.
sast-fileupload
Detect insecure file upload vulnerabilities in a codebase using a three-phase approach: discovery (find all upload sites), batched verify (check extension bypass and related issues in parallel subagents, 3 sites each), and merge (consolidate batch results). Requires sast/architecture.md (run sast-analysis first).…