Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkillsnpx agentmods add skills/crestapps/crestapps.agentskills/orchardcore-asset-managerWrote 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-asset-manager)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-asset-manager"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-asset-manager/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-asset-manager"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-asset-manager.svg" alt="Reviewed on agentmods" width="80" 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.00094 | $0.02842 |
| Opus 5 | $0.00047 | $0.01421 |
| Sonnet 5 | $0.00019 | $0.00568 |
| Haiku 4.5 | $0.00009 | $0.00284 |
Grade A, and why
orchardcore-asset-manager 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 6d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Asset Manager
Use the Orchard Core Asset Manager for frontend assets in Orchard Core 3.0 modules and themes. It is based on Concurrently, so it can run shell commands as well as Parcel, Vite, Webpack, Sass, minification, concatenation, and copy actions. Definitions live in Assets.json files and the tool uses ES modules (.mjs) for its own configuration.
Scope and transition from Gulp
- This skill covers the framework's development asset pipeline for Orchard Core modules and themes. It does not cover the Media module's runtime media storage or image processing.
- Orchard Core 3.0 introduces the Asset Manager to gradually replace the Gulp pipeline.
- Gulp remains available for backward compatibility while existing projects transition. Use the Asset Manager for new work and migrate a Gulp pipeline when its output and resource references have been verified.
- The Asset Manager builds files into
wwwroot; it does not register those files with Orchard Core's Resource Management system. Keep the existing resource manifest or tag helper registration and point it to the generated files.
Prerequisites and project setup
-
Install the Node.js LTS version required by the repository. For the Orchard Core 3.0 repository, use the version in the root
.node-versionfile (the current documentation specifies Node.js 24.x LTS). -
From the repository root, enable Corepack and install workspace dependencies:
corepack enable yarnVerify that the Yarn version matches the
packageManagervalue in the rootpackage.json. If Node.js came from a distributor without Corepack, install Corepack first withnpm install -g corepack. -
Keep the three package responsibilities separate:
Location Responsibility Root package.jsonYarn workspaces, top-level scripts, general development dependencies, and optional resolutions.scripts/assets-manager/package.jsonAsset Manager CLI and build tools such as Parcel, Vite, Webpack, Sass, and PostCSS Module or theme Assets/package.jsonRuntime frontend dependencies shipped by that module or theme
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.
- 6d ago First seen · 244 lines · 94 tokens per session scan A aa31c14a1769
orchardcore-asset-manager is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 11d ago), licensed MIT. It adds 94 tokens to every session and 2,842 once invoked, about $0.0005 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
polish-ui
Design-quality workflow that combines design taste, aesthetic direction, image-to-code, a Web Interface Guidelines audit, and real-browser verification. Use when building or polishing a UI surface, implementing a mockup/screenshot, or when asked to make a page "look great".
add-permission
Add a permission constant across backend and frontend.
biome
Use Biome in .NET repositories that ship Node-based frontend assets and want a fast combined formatter-linter-import organizer for JavaScript, TypeScript, CSS, JSON, GraphQL, or HTML. USE FOR: biome.json or @biomejs/biome setup; fast frontend formatting and linting; replacing overlapping frontend style tools…
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.
sfcc-sfra-scss
Best practices for styling and theming SFRA storefronts using SCSS. Use when asked to create style overrides, theming, responsive layouts, or CSS customizations in SFCC.