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-content-access-controlgit 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-content-access-control)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-content-access-control"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-content-access-control.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.00176 | $0.01482 |
| Opus 5 | $0.00088 | $0.00741 |
| Sonnet 5 | $0.00035 | $0.00296 |
| Haiku 4.5 | $0.00018 | $0.00148 |
Grade A, and why
orchardcore-content-access-control 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Content Access Control - Prompt Templates
Configure Content Access Control
You are an Orchard Core expert. Generate code, configuration, and recipes for restricting content access by role in an Orchard Core application using the CrestApps Content Access Control module.
Overview
The Content Access Control module (CrestApps.OrchardCore.ContentAccessControl) lets you restrict which users can view specific content items based on their assigned roles. When enabled, content editors can pick roles on any content type that includes a RolePickerPart, and only users belonging to at least one of the selected roles will be authorized to view that content.
- Feature ID -
CrestApps.OrchardCore.ContentAccessControl - Module category - Content Management
- Dependency -
CrestApps.OrchardCore.Roles(automatically included when you install the NuGet package) - NuGet package -
CrestApps.OrchardCore.ContentAccessControl
How It Works
- The module registers a
RoleBasedContentItemAuthorizationHandleras a scopedIAuthorizationHandler. - When Orchard Core checks the
ViewContentpermission for a content item, the handler inspects everyRolePickerPartattached to that content type. - For each
RolePickerPartwhoseRolePickerPartContentAccessControlSettings.IsContentRestrictedflag is enabled, the handler collects the role names stored on the content item. - If the current user belongs to at least one of those roles, the handler calls
context.Succeed(requirement)and grants access. - If no restricted
RolePickerPartis found or no roles are configured, the handler does nothing and defers to the default authorization pipeline.
Key Services
| Service | Lifetime | Purpose |
|---|---|---|
RoleBasedContentItemAuthorizationHandler |
Scoped | Intercepts ViewContent permission checks and enforces role-based restrictions |
RolePickerPartContentAccessControlSettingsDisplayDriver |
Scoped | Provides the "Restrict content?" checkbox in the content type editor for each RolePickerPart |
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 First seen · 145 lines · 176 tokens per session scan A 651e2dd5069a
orchardcore-content-access-control is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 10d ago), licensed MIT. It adds 176 tokens to every session and 1,482 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).…