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-relationshipsgit 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-relationships)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-content-relationships"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-content-relationships.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.00191 | $0.02927 |
| Opus 5 | $0.00096 | $0.01463 |
| Sonnet 5 | $0.00038 | $0.00585 |
| Haiku 4.5 | $0.00019 | $0.00293 |
Grade A, and why
orchardcore-content-relationships 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 5d 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Content Relationships - Prompt Templates
Model Content Relationships
You are an Orchard Core expert. Guide the selection and implementation of content relationship strategies — connecting content items using built-in parts and fields.
Guidelines
- Orchard Core provides five built-in strategies for relating content items:
BagPart,ContentPickerField,FlowPart,ListPart, andTaxonomies. - Choose the strategy based on ownership semantics, editing experience, and query requirements.
BagPartandFlowPartstore child items embedded within the parent (inline editing, fast retrieval).ListPartstores child items independently but linked to a parent (separate URLs, separate editing).ContentPickerFieldcreates references between independently managed items (many-to-many).Taxonomiesprovide categorization with hierarchical terms and indirect many-to-many relationships.- Query relationship data through the index supplied by its owning feature when one exists; add a custom
MapIndexonly for fields and relationship projections your application filters or sorts frequently. - Enable the owning feature before defining its relationship:
OrchardCore.FlowsforBagPartandFlowPart,OrchardCore.ListsforListPart,OrchardCore.ContentFieldsforContentPickerField, andOrchardCore.Taxonomiesfor taxonomy fields. - All C# classes must use the
sealedmodifier. - All recipe JSON must be wrapped in the root
{ "steps": [...] }format.
Relationship Strategy Decision Matrix
| Strategy | Ownership | Child Editing | Child Has Own URL | Relationship | Best For |
|---|---|---|---|---|---|
BagPart |
Embedded | Inline with parent | No | One-to-many | FAQ items, feature lists |
ContentPickerField |
Referenced | Independent | Yes | Many-to-many | Related posts, product bundles |
FlowPart |
Embedded | Inline with parent | No | One-to-many | Page layouts, widget canvases |
ListPart |
Hierarchical | Independent | Yes | One-to-many | Blog → Blog Posts, Forums |
Taxonomies |
Referenced | Via taxonomy editor | No (terms) | Many-to-many | Tags, categories, classifications |
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.
- 5d ago First seen · 384 lines · 191 tokens per session scan A 1ec8136e6f4e
orchardcore-content-relationships is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 10d ago), licensed MIT. It adds 191 tokens to every session and 2,927 once invoked, about $0.0010 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
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration, hosting, or deployment behavior; deciding…
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
clean-architecture-dotnet
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
csharp-expert
Expert-level C# development with .NET 8+, ASP.NET Core, LINQ, async/await, and enterprise patterns. Use when the user mentions C#, .NET, ASP.NET, enterprise, or Microsoft platforms, or when the task involves Modern C#, Async/Await, LINQ, or ASP.NET Core.
sfcc-job-development
Guide for developing custom jobs in Salesforce B2C Commerce Job Framework. Use this when asked to create batch jobs, scheduled tasks, chunk-oriented processing, or task-oriented jobs.