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 agentmods add skills/crestapps/crestapps.agentskills/orchardcore-content-fieldsnpx skills add CrestApps/CrestApps.AgentSkills --skill orchardcore-content-fieldsgit 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-fields)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-content-fields"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-content-fields.svg" alt="Measured on agentmods" 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 | $0.00189 | $0.05363 |
| Opus 5 | $0.00095 | $0.02681 |
| Sonnet 5 | $0.00038 | $0.01073 |
| Haiku 4.5 | $0.00019 | $0.00536 |
Grade A, and why
orchardcore-content-fields 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 — 689 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Content Fields - Prompt Templates
Add and Configure Content Fields
You are an Orchard Core expert. Generate migration code and recipes for common content fields and verify feature-specific options against the enabled module.
Guidelines
- Fields are added to content parts using
AlterPartDefinitionAsyncin a migration. - Each field has a
FieldSettingsbase withHint(string) andRequired(bool). - Each field type has its own specific settings class (e.g.,
TextFieldSettings,NumericFieldSettings). - Fields also have
ContentPartFieldSettingscontrollingDisplayName,Description,Editor,DisplayMode, andPosition. - Use
.WithEditor("EditorName")to select an editor variant. - Use
.WithDisplayMode("DisplayModeName")to select a display variant. - Third-party modules providing fields (CrestApps, Lombiq, community modules, etc.) must be installed as NuGet packages in the web project (the startup project of the solution), not just in the module project.
- Always seal classes.
General Pattern for Adding a Field
await _contentDefinitionManager.AlterPartDefinitionAsync("{{PartName}}", part => part
.WithField("{{FieldName}}", field => field
.OfType("{{FieldType}}")
.WithDisplayName("{{DisplayName}}")
.WithDescription("{{Description}}")
.WithPosition("{{Position}}")
.WithSettings(new {{FieldType}}Settings
{
// Field-specific settings
})
)
);
TextField
Stores a single text value. Supports multiple editor modes.
TextField Settings
| Setting | Type | Default | Description |
|---|---|---|---|
Hint |
string | null |
Help text displayed below the field. |
Required |
bool | false |
Whether the field is required. |
DefaultValue |
string | null |
Default value for new content items. |
Type |
FieldBehaviorType | Unset |
Field behavior type. |
Pattern |
string | null |
The pattern used to build the value. |
Placeholder |
string | "" |
Placeholder text. |
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 First seen · 689 lines · 189 tokens per session scan A c0b4a652eddf
orchardcore-content-fields is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 7d ago), licensed MIT. It adds 189 tokens to every session and 5,363 once invoked, about $0.0009 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
prepare-release
Prepare a new release for the C# MCP SDK. Assesses Semantic Versioning level (PATCH/MINOR/MAJOR), bumps the version, runs ApiCompat and ApiDiff, reviews documentation, updates changelogs, drafts release notes, and creates a pull request with all release artifacts. Use when asked to prepare a release, start a release…
publish-release
Publish a GitHub release for the C# MCP SDK after a prepare-release PR has been merged. Refreshes release notes to include any PRs merged since preparation, warns about version or breaking change impacts from late-arriving PRs, and creates a draft GitHub release. Use when asked to publish a release, finalize a…
verify-release
Verify a published release of the C# MCP SDK. Monitors the Release and Publish Docs workflows triggered by publishing a GitHub release, confirms the packages are listed on NuGet.org, and confirms the versioned documentation site reflects the release. Use when asked to verify a release, check whether a release…
bump-version
Assess and bump the SDK version using Semantic Versioning 2.0.0. Evaluates queued changes to recommend PATCH/MINOR/MAJOR, updates src/Directory.Build.props, and creates a pull request. Owns the SemVer assessment logic shared by prepare-release and publish-release. Use when asked to bump the version, assess the…
breaking-changes
Audit pull requests for breaking changes in the C# MCP SDK. Examines PR descriptions, review comments, and diffs to identify API and behavioral breaking changes, then reconciles labels with user confirmation. Use when asked to audit breaking changes, check for breaking changes, or review a set of PRs for breaking…
run-conformance-from-branch
Run MCP conformance tests in the C# SDK against a conformance branch (including forks) instead of the published npm version, then restore pinned dependencies.