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/marcusquinn/aidevops/cloudron-app-packagingnpx skills add marcusquinn/aidevops --skill cloudron-app-packaginggit clone --depth 1 https://github.com/marcusquinn/aidevopsWrote 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/marcusquinn/aidevops/cloudron-app-packaging)<a href="https://agentmods.dev/skills/marcusquinn/aidevops/cloudron-app-packaging"><img src="https://agentmods.dev/badge/skills/marcusquinn/aidevops/cloudron-app-packaging.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.00023 | $0.03047 |
| Opus 5 | $0.00012 | $0.01523 |
| Sonnet 5 | $0.00005 | $0.00609 |
| Haiku 4.5 | $0.00002 | $0.00305 |
Grade A, and why
cloudron-app-packaging 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudron App Packaging (Official Skill)
Cloudron apps are Docker images plus CloudronManifest.json. The platform provides a readonly filesystem, addon services, and a managed backup/restore lifecycle.
Quick Reference
- Upstream: git.cloudron.io/docs/skills (
cloudron-app-packaging) | docs.cloudron.io/packaging - Reference files:
cloudron-app-packaging-skill/manifest-ref.md,cloudron-app-packaging-skill/addons-ref.md - Also see:
cloudron-app-packaging.md(native aidevops guide: helpers, local dev, Dockerfile/start.sh patterns, pre-packaging checks) andcloudron-app-publishing-skill.md(required version catalog, public metadata, keyless image/catalog provenance, visual assets, and publication lifecycle) - Last upstream review:
f35dab45cc31("backupCommand, restoreCommand skill"); adopted current base-image, Node PATH, PHP, builder, and backup/restore lifecycle guidance.
npm install -g cloudron
cloudron login my.example.com
cloudron init # creates CloudronManifest.json and Dockerfile
cloudron install # uploads source, builds on server, installs app
cloudron update # re-uploads, rebuilds, updates running app
# For any independently distributed package, initialize and maintain
# CloudronVersions.json and keyless release provenance using
# cloudron-app-publishing-skill.md.
Key Constraints
| Constraint | Detail |
|---|---|
| Filesystem readonly | Writable: /tmp, /run (ephemeral), /app/data (persisted, requires localstorage addon) |
| Addons for services | Databases, caching, email, auth via addons — env vars injected at runtime, re-read every start |
| Manifest declares all | CloudronManifest.json: metadata, ports, addon requirements |
| HTTP only | App listens HTTP — platform handles TLS |
| Memory default | 256 MB (RAM + swap). Set memoryLimit in manifest |
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 · 238 lines · 23 tokens per session scan A e8ce4dbd5d09
cloudron-app-packaging is a skill published in the GitHub repository marcusquinn/aidevops (392 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 3,047 once invoked, about $0.0001 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
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
azure-prepare
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd…
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
aws-cloudformation-ecs
Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service discovery, monitoring, logging, template structure, parameters, outputs, and cross-stack references. Use when creating ECS…
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations.