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-crestapps-resourcesgit 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-resources)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-crestapps-resources"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-crestapps-resources.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.00143 | $0.01773 |
| Opus 5 | $0.00072 | $0.00886 |
| Sonnet 5 | $0.00029 | $0.00355 |
| Haiku 4.5 | $0.00014 | $0.00177 |
Grade A, and why
orchardcore-crestapps-resources 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrestApps Resources
Consume CrestApps shared frontend resources
You are an Orchard Core expert. Use CrestApps.OrchardCore.Resources as the shared resource manifest for CrestApps modules. It registers known resource names with Orchard Core Resource Management. Consumers request a resource by name and let Orchard Core select local URLs or configured CDN behavior.
Guidelines
- Install
CrestApps.OrchardCore.Resourcesin the web or startup project when an application directly depends on its assets. - Enable the exact
CrestApps.OrchardCore.Resourcesfeature. Other CrestApps features can bring it in through their manifest dependencies. - Request resources by their registered names. Do not hardcode the module's virtual asset paths in a theme or module.
- Use Orchard Core resource tag helpers in Razor so resource management controls rendering and placement.
- Prefer the existing
intl-tel-inputscript and style forPhoneField; the Content Fields module already depends on this feature. - CDN-capable resources define local URLs, CDN URLs, versions, and for many resources integrity values. Keep browser CSP and SRI policies compatible with those declarations.
- Resources without a CDN declaration such as
item-selectorandlist-management-uiare served from the module's local static assets. - Do not define another manifest entry with an existing name. That makes selection and ordering ambiguous.
- Do not copy vendor files into a consuming module merely to use one of the registered names.
- Resource registration is not a content-feature enablement substitute. Enable the module that owns application behavior separately.
- When adding a new shared resource to this module, add the manifest declaration and local static assets together, then use a unique stable name.
Feature overview
| Feature ID | Purpose |
|---|---|
CrestApps.OrchardCore.Resources |
Shared Orchard Core script and stylesheet resource manifest |
Enable shared resources
{
"steps": [
{
"name": "Feature",
"enable": [
"CrestApps.OrchardCore.Resources"
],
"disable": []
}
]
}
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 · 161 lines · 143 tokens per session scan A a224ec82bcea
orchardcore-crestapps-resources is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 10d ago), licensed MIT. It adds 143 tokens to every session and 1,773 once invoked, about $0.0007 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
add-permission
Add a permission constant across backend and frontend.
engram-dashboard-htmx
HTMX and templ interaction rules for the Engram dashboard. Trigger: Any change to htmx attributes, partial updates, forms, or server-rendered browser UI.
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…
gen-types
Regenerate frontend API types from the backend OpenAPI spec.
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.