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-itemsgit 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-items)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-content-items"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-content-items/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-content-items"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-content-items.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.00179 | $0.03213 |
| Opus 5.5 | $0.00072 | $0.01285 |
| Sonnet 5.5 | $0.00036 | $0.00643 |
| Haiku 4.5 | $0.00018 | $0.00321 |
Grade A, and why
orchardcore-content-items 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 yesterday.
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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Content Items - Prompt Templates
Working with Content Items
You are an Orchard Core expert. Generate code and configuration for managing content items in Orchard Core.
Guidelines
- Content items are the fundamental data units in Orchard Core, composed of parts and fields.
- Every content item has a
ContentItemId(stable across versions) and aContentItemVersionId(unique per version). - Use
IContentManagerfor all content item CRUD operations; do not manipulate the database directly. ValidateAsyncreturns aContentValidateResultand does not cancel the current session. If validation follows a mutation, callISession.CancelAsync()explicitly when the result fails.RemoveAsyncreturnsfalsewhen a removing handler cancels the operation.- Content items support draft and published states when the content type is configured as
Draftable. - Content items support versioning when the content type is configured as
Versionable. - Always call
await ISession.SaveChangesAsync()or let the request pipeline flush changes when modifying content outside ofIContentManager. - Use
IContentHandlerto hook into lifecycle events such as creating, publishing, and removing content. - Enable
OrchardCore.Contentsfor the content-management UI and API endpoints. Content-management APIs are registered by the application framework and consumed throughIContentManager.
Content Item Lifecycle
A content item progresses through the following states:
- New - Created in memory with
NewAsync, not yet persisted. - Draft - Saved but not published. Only visible to editors.
- Published - Live and visible to all users. Sets
Published = trueandLatest = true. - Unpublished - Previously published, now reverted to draft state.
- Removed - Soft-deleted from the system.
When a published content item is edited, a new draft version is created while the published version remains live. Publishing the draft replaces the previous published version.
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.
- yesterday Changed · +20 lines · -15 tokens per session fbf88059ef1b
- 1mo ago First seen · 370 lines · 194 tokens per session scan A b7c29d858fd9
orchardcore-content-items is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed today), licensed MIT. It adds 179 tokens to every session and 3,213 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
sast-idor
Detect Insecure Direct Object Reference (IDOR) vulnerabilities in a codebase using a three-phase approach: recon (find candidates), batched verify (check authorization in parallel subagents, 3 candidates each), and merge (consolidate batch results). Checks endpoints for missing ownership or authorization checks on…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
add-service
Scaffold a new service integration. Use when the user asks to add a service, integrate an external API, or create a reusable domain module with its own initialization and state.
api-utils
API reference for all utilities exported from @cyanheads/mcp-ts-core/utils. Use when looking up utility method signatures, options, peer dependencies, or usage patterns.
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.