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-admin-edit-viewsgit 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-admin-edit-views)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-admin-edit-views"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-admin-edit-views/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-admin-edit-views"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-admin-edit-views.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.00218 | $0.05399 |
| Opus 5.5 | $0.00087 | $0.02160 |
| Sonnet 5.5 | $0.00044 | $0.01080 |
| Haiku 4.5 | $0.00022 | $0.00540 |
Grade A, and why
orchardcore-admin-edit-views 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 today.
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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Admin Edit Views
Every admin view that edits something (a content part or field, a settings group, a workflow activity, a deployment step, or a module's own entity) lays out its rows with the static ocat- (Orchard Core Admin Theme) CSS classes. TheAdmin styles them as a stacked Bootstrap form; a custom admin theme can restyle every editor (for example as a horizontal form) by overriding the classes, without touching any view.
- Use
ocat-*only in admin views. Never in front-end views (Login, Register, ForgotPassword, or anything rendered by the site theme). - Do not use Bootstrap-only row markup (
mb-3,form-group,form-label) for admin field rows, and do not use the@Orchard.GetWrapperClasses()-style helpers (removed in Orchard Core 3.0). - Admin pages that list items are not edit views; they render
<admin-list>(seeorchardcore-admin-lists).
Which Views This Covers
| Editor | Produced by | View file |
|---|---|---|
| Content part editor | ContentPartDisplayDriver<TPart>.Edit with GetEditorShapeType(context) |
Views/{Part}.Edit.cshtml |
| Content field editor | ContentFieldDisplayDriver<TField>.Edit with GetEditorShapeType(context) |
Views/{Field}.Edit.cshtml |
| Field editor variant | The field's Editor setting | Views/{Field}-{Editor}.Edit.cshtml plus Views/{Field}-{Editor}.Option.cshtml (the <option> shown in the editor dropdown) |
| Part settings (per content type) | ContentTypePartDefinitionDisplayDriver<TPart> returning "{Part}Settings_Edit" at Content |
Views/{Part}Settings.Edit.cshtml |
| Field settings | ContentPartFieldDefinitionDisplayDriver<TField> returning "{Field}Settings_Edit" at Content |
Views/{Field}Settings.Edit.cshtml |
| Site settings group | SiteDisplayDriver<TSettings> with .OnGroup(...) |
Views/{Name}Settings.Edit.cshtml |
| Workflow activity, deployment step | ActivityDisplayDriver / DeploymentStepDisplayDriver ({Name}_Fields_Edit) |
Views/Items/{Name}.Fields.Edit.cshtml |
| Module entity page | Your admin controller action | Views/{Controller}/Edit.cshtml, Create.cshtml |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 393 lines · 218 tokens per session scan A 6ad6ecddf268
orchardcore-admin-edit-views is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed today), licensed MIT. It adds 218 tokens to every session and 5,399 once invoked, about $0.0009 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-10-22.
Other skills, from other repositories
metalint
Use Metalint in .NET repositories that ship Node-based frontend assets and want one CLI entrypoint over several underlying linters. USE FOR: unified frontend lint commands; combined ESLint, Stylelint, HTMLHint, or similar checks; CI orchestration over multiple frontend linters. DO NOT USE FOR: simple repos where Biome…
review-design
Reviews frontend components for design quality and UI/UX standards. Use when checking component styling, responsiveness, accessibility, or when asked to review a design.
powerpoint-cli
Discover and use the PowerPoint CLI plugin to automate a live PowerPoint desktop session. Use for terminal, PowerShell, batch, and coding-agent tasks; not general presentation design. Triggers: pptcli, PowerPoint command line, presentation automation script.
powerpoint-deck-design
Plan or improve the visual design of a PowerPoint presentation: layout, typography, color, hierarchy, accessibility, and consistency. Use when the user asks to create, redesign, or review how a deck looks; not for general PowerPoint automation or content-only edits.
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…
motion-design
Canonical motion and animation design covering foundations, patterns, advanced dynamics, and framework transitions.