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 agentmods add skills/crestapps/crestapps.agentskills/orchardcore-crestapps-usersnpx skills add CrestApps/CrestApps.AgentSkills --skill orchardcore-crestapps-usersgit 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-crestapps-users)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-crestapps-users"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-crestapps-users.svg" alt="Measured on agentmods" 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.02053 |
| Opus 5 | $0.00083 | $0.01026 |
| Sonnet 5 | $0.00033 | $0.00411 |
| Haiku 4.5 | $0.00017 | $0.00205 |
Grade A, and why
orchardcore-crestapps-users 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 2d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrestApps Users
Configure enhanced user experiences
You are an Orchard Core expert. Use CrestApps Users to add cached user components, configurable display names, user-name-aware searching and picker labels, and media-backed user avatars. Treat the core feature as an internal dependency feature and enable the specific Display Name or Avatar capability required by the tenant.
Guidelines
- Install
CrestApps.OrchardCore.Usersin the web or startup project. CrestApps.OrchardCore.Usersis enabled by dependency only. Enable the exact public feature IDsCrestApps.OrchardCore.Users.DisplayNameand orCrestApps.OrchardCore.Users.Avatars.- Display Name depends on
OrchardCore.ContentFieldsand the CrestApps Users core feature. - Avatars depend on
OrchardCore.Mediaand the CrestApps Users core feature. UserFullNamePartstoresDisplayName,FirstName,MiddleName, andLastNameon the Orchard CoreUser.- Resolve a user label through
IDisplayNameProvider.GetAsync()rather than reproducing name-format logic in every view. - The display-name provider falls back to
UserNamewhen the user is not an Orchard CoreUser, the full-name part is absent, or no configured name can be generated. - Configure display-name format under Settings → User Display Name. Its custom format option uses Liquid and must validate before it is saved.
- With
OrchardCore.Liquidenabled, use thedisplay_nameLiquid filter to resolve the configured display name. - The Display Name feature replaces the default user-picker result provider and extends the users admin list search to display name and full-name fields.
- The avatar editor requires
MediaPermissions.ManageMedia. It restricts allowed media types to image extensions from Orchard Core media options. - Use
IndexUsersto resave users in batches when user indexes must be refreshed. The handler caps a positive requested batch size at 1000. - Enable CrestApps Recipes when you need
UserFullNamePartschema support in content recipes.
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.
- 2d ago First seen · 198 lines · 166 tokens per session scan A 00014340ebc7
orchardcore-crestapps-users is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 7d ago), licensed MIT. It adds 166 tokens to every session and 2,053 once invoked, about $0.0008 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
prepare-release
Prepare a new release for the C# MCP SDK. Assesses Semantic Versioning level (PATCH/MINOR/MAJOR), bumps the version, runs ApiCompat and ApiDiff, reviews documentation, updates changelogs, drafts release notes, and creates a pull request with all release artifacts. Use when asked to prepare a release, start a release…
publish-release
Publish a GitHub release for the C# MCP SDK after a prepare-release PR has been merged. Refreshes release notes to include any PRs merged since preparation, warns about version or breaking change impacts from late-arriving PRs, and creates a draft GitHub release. Use when asked to publish a release, finalize a…
verify-release
Verify a published release of the C# MCP SDK. Monitors the Release and Publish Docs workflows triggered by publishing a GitHub release, confirms the packages are listed on NuGet.org, and confirms the versioned documentation site reflects the release. Use when asked to verify a release, check whether a release…
bump-version
Assess and bump the SDK version using Semantic Versioning 2.0.0. Evaluates queued changes to recommend PATCH/MINOR/MAJOR, updates src/Directory.Build.props, and creates a pull request. Owns the SemVer assessment logic shared by prepare-release and publish-release. Use when asked to bump the version, assess the…
breaking-changes
Audit pull requests for breaking changes in the C# MCP SDK. Examines PR descriptions, review comments, and diffs to identify API and behavioral breaking changes, then reconciles labels with user confirmation. Use when asked to audit breaking changes, check for breaking changes, or review a set of PRs for breaking…
run-conformance-from-branch
Run MCP conformance tests in the C# SDK against a conformance branch (including forks) instead of the published npm version, then restore pinned dependencies.