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-data-pipeline-stepsgit 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-data-pipeline-steps)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-data-pipeline-steps"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-data-pipeline-steps/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-data-pipeline-steps"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-data-pipeline-steps.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00212 | $0.05822 |
| Opus 5.5 | $0.00085 | $0.02329 |
| Sonnet 5.5 | $0.00042 | $0.01164 |
| Haiku 4.5 | $0.00021 | $0.00582 |
Grade A, and why
orchardcore-data-pipeline-steps 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 today.
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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Data Pipeline Steps (extending Data Pipelines)
Modules extend the Data Pipelines module (Orchard Core 4.0) with services registered in their startup. This skill covers step types and everything around them. Using the module: orchardcore-data-pipelines. Data sources and file formats: orchardcore-data-sources. Formula functions and filter conditions: orchardcore-data-formulas.
Extension points
| To add | Implement | Register |
|---|---|---|
| A transform (mask, enrich), source or destination | DataPipelineStepType<TStep, TSettings>, IDataPipelineStepType |
services.AddDataPipelineStep<TStep, TDriver>() |
| A transform that sees every row first (sort-like) | A step type with DataPipelineRowReader and the data operations |
same |
| The editor of a step | DataPipelineStepDisplayDriver<TSettings, TViewModel> + views |
with its step type |
| The icon of a step type | DataPipelineStepIcon-{StepName}.cshtml |
|
| Values kept between runs | context.GetState / context.SetState |
|
| Work confirmed when a run succeeds | context.Run.OnSucceeded |
|
| Reactions to pipeline publish/delete | IDataPipelineHandler |
services.AddScoped<IDataPipelineHandler, T>() |
| Reactions to the end of runs | IDataPipelineRunHandler |
services.AddScoped<IDataPipelineRunHandler, T>() |
| Links to a module resource | ISharedLinkHandler |
services.AddSharedLinkHandler<T>() |
Packages and dependencies
Install OrchardCore.DataPipelines in the web/startup project. The module project references what it uses (version 4.*):
| Package | Provides |
|---|---|
OrchardCore.DataPipelines.Abstractions |
DataPipelineStepType<,>, IDataPipelineStepType, contexts, ports, DataPipelineStep, shared link abstractions and AddSharedLinkHandler |
OrchardCore.DataPipelines.Core |
AddDataPipelineStepType<T>(), DataPipelineRowReader, DataPipelineFormulas, DataPipelineOptions, IDataTimeZoneResolver |
OrchardCore.DataPipelines |
DataPipelineStepDisplayDriver<,>, AddDataPipelineStep<,>(), DataPipelineEditorContext, DataPipelineSecrets, IDataPipelineHandler, IDataPipelineRunHandler, DataPipelineStateManager |
OrchardCore.DataSources.Abstractions / .Core |
DataField, DataBatch, DataFieldType, data operations |
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.
- today First seen · 368 lines · 212 tokens per session scan A 3bc8e7906b0d
orchardcore-data-pipeline-steps is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed today), licensed MIT. It adds 212 tokens to every session and 5,822 once invoked, about $0.0008 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-10-22.
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.