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 KhaledSaeed18/dotclaude --skill coolify-image-appgit clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/coolify-image-app)<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/coolify-image-app"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/coolify-image-app/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/khaledsaeed18/dotclaude/coolify-image-app"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/coolify-image-app.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.00051 | $0.01025 |
| Opus 5.5 | $0.00020 | $0.00410 |
| Sonnet 5.5 | $0.00010 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade B, and why
coolify-image-app scanned grade B with 2 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 11d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
C=$(sudo docker ps --filter label=coolify.resourceName=<app> --format '{{.Names}}' | head -1) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Coolify rejects shell operators (`&&`, `|`, `;`) in the health command, and the runtime image has no curl: the probe must be a plain binary call. Number inputs sometimes do not take a typed value; press Enter inside the How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A Coolify application of type Docker Image is the contract between the pipeline and the server: the pipeline moves one field (the image tag) and asks for a deploy; Coolify does the rolling update behind one domain with the container's own probe as the gate. Configure it once, exactly, and let every later deploy be an API call.
Hard rules: never break these
- Creating or saving a Coolify resource is a production action. Confirm with the owner before creating, deploying, changing domains or deleting anything, unless they already authorised it for this task.
- Never publish host ports and never set a custom container name. Port mapping bypasses the firewall; a fixed name breaks rolling updates.
- The image must exist before the first deploy. Push
:mainfrom the pipeline (or a manual run) first; Coolify cannot build a Docker Image app. - Never type or print a token or secret. The owner creates API tokens and pastes secrets; you prefill forms and give click-by-click steps.
- Verify every save by reloading. Coolify's forms sometimes accept input without persisting it; reload the page and read the value back before moving on.
Step 1: Gather the facts
From the repo and the coolify-vps-baseline record: project and environment names, the image reference (ghcr.io/<owner>/<repo>), the container port, the exact domain, the health probe command the image ships (node healthcheck.js or similar), the memory budget, and which environment variables are runtime (build-time ones are baked into the image and must not be set here).
Step 2: Create the application
Coolify UI, the project's environment, New resource, Docker Image: image name without a tag, tag main, Create application. Note the application UUID from the URL; the pipeline needs it.
Step 3: Configure, tab by tab
| Tab | Set | Why |
|---|---|---|
| General | Name <app>; Domains https://<domain> only, delete the sslip.io one; Port <port>; no port mappings; no custom name |
one router, one domain, no host ports |
| Healthcheck | Type Container command; command node healthcheck.js; interval 30, timeout 5, retries 3, start period 15; then Enable and confirm the modal |
the container, not the proxy, decides readiness |
| Resource Limits | Memory 512m (or the budget); leave CPU |
one runaway app cannot take the host |
| Environment Variables | runtime variables only; mark secrets as such | build-time values are already in the image |
| Rollback | nothing to set; this is where an earlier tag is redeployed | the rollback path |
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.
- 11d ago First seen · 53 lines · 51 tokens per session scan B 47dd08c600ff
coolify-image-app is a skill published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 1,025 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-05.
Other skills, from other repositories
agents-v2-py
Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.
kubernetes
Expert in Kubernetes and DevOps with infrastructure-as-code and cloud-native patterns.
security-hardening
Reduces attack surface across OS, container, cloud, network, and database layers using CIS Benchmarks and zero-trust principles. Use when hardening production infrastructure, meeting compliance requirements, or implementing defense-in-depth security.
deploying-applications
Deployment patterns from Kubernetes to serverless and edge functions. Use when deploying applications, setting up CI/CD, or managing infrastructure. Covers Kubernetes (Helm, ArgoCD), serverless (Vercel, Lambda), edge (Cloudflare Workers, Deno), IaC (Pulumi, OpenTofu, SST), and GitOps patterns.
apify-actor-development
Important: Before you begin, fill in the generatedBy property in the meta section of .actor/actor.json. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonnet 4.5". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.
apify-actorization
Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output.