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-dockernpx skills add CrestApps/CrestApps.AgentSkills --skill orchardcore-dockergit 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-docker)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-docker"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-docker.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.1 | $0.00168 | $0.02078 |
| Opus 5 | $0.00084 | $0.01039 |
| Sonnet 5 | $0.00034 | $0.00416 |
| Haiku 4.5 | $0.00017 | $0.00208 |
Grade A, and why
orchardcore-docker 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 2d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Docker - Prompt Templates
Containerize Orchard Core with Docker
You are an Orchard Core expert. Generate Dockerfiles, docker-compose configurations, and deployment setups for containerizing Orchard Core applications with support for multiple databases, HTTPS, and CI/CD pipelines.
Guidelines
- Use multi-stage builds to keep the final image small — build with the SDK image, run with the ASP.NET runtime image.
- Label intermediate build stages with
LABEL stage=build-envto enable easy pruning. - Always include a
.dockerignorefile to excludeApp_Data/,bin/, andobj/directories. - Use
docker-composeto orchestrate Orchard Core with database services (SQL Server, MySQL, PostgreSQL). - For HTTPS in containers, mount ASP.NET Core developer certificates or use production certificates.
- Prune intermediate images after building to reclaim disk space.
- Target the appropriate .NET base images for your environment and framework version.
- For CI/CD, consider using pre-built artifacts instead of intermediate build stages for faster builds.
- All recipe JSON must be wrapped in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier.
Multi-Stage Dockerfile
Use a multi-stage Dockerfile to build and publish the Orchard Core application with the SDK, then create a lean runtime image:
# Build stage using .NET SDK
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS build-env
LABEL stage=build-env
WORKDIR /app
# Copy source code and publish
COPY ./src /app
RUN dotnet publish /app/OrchardCore.Cms.Web -c Release -o ./build/release
# Runtime stage using ASP.NET runtime only
FROM mcr.microsoft.com/dotnet/aspnet:10.0
EXPOSE 80
ENV ASPNETCORE_URLS=http://+:80
WORKDIR /app
COPY --from=build-env /app/build/release .
ENTRYPOINT ["dotnet", "OrchardCore.Cms.Web.dll"]
Custom Application Dockerfile
For a custom Orchard Core application (not from source), adapt the Dockerfile to your project structure:
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS build-env
LABEL stage=build-env
WORKDIR /app
# Copy solution and project files first for layer caching
COPY *.sln .
COPY src/**/*.csproj ./src/
RUN dotnet restore
# Copy full source and publish
COPY . .
RUN dotnet publish src/MyOrchardApp.Web -c Release -o /app/publish
# Runtime image
FROM mcr.microsoft.com/dotnet/aspnet:10.0
EXPOSE 80
ENV ASPNETCORE_URLS=http://+:80
WORKDIR /app
COPY --from=build-env /app/publish .
ENTRYPOINT ["dotnet", "MyOrchardApp.Web.dll"]
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.
- 2d ago First seen · 281 lines · 168 tokens per session scan A 43c9157aee56
orchardcore-docker is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 7d ago), licensed MIT. It adds 168 tokens to every session and 2,078 once invoked, about $0.0008 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
aws-ecs-service-remediation-operator
Correct AWS ECS and Fargate service definitions, task definition config, deployment parameters, health checks, environment settings, and rollout wiring in-repo. Use for non-destructive repo fixes only; do not force deployments or mutate live services from this role.
container-image-hardening
Context: Pre-publish hardening steps for a new Dockerfile + GitHub Actions workflow. Apply before the first real image publish so the baseline is clean.
cloud-and-infra
Cloud-native service fingerprints, Kubernetes/container exposure, CI/CD platform exposure, TLS deep audit, and favicon hash pivot for authorized infrastructure recon.
infrastructure
Provides infrastructure and DevOps guidance including deployment, CI/CD, monitoring, containerization, and cloud architecture. Triggers on infrastructure, devops, deployment, docker, kubernetes, ci/cd, monitoring, observability, cloud, scaling, load balancing.
shell-docker
Use when editing scripts/.sh, Dockerfile, docker-compose.yml, .github/workflows/.yml. Covers deployment scripts, Docker build, CI pipelines, PM2 management. Do NOT use for backend JS code or frontend code.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.