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/catalystbyzoho/claude-plugin/catalyst-appsailnpx skills add catalystbyzoho/claude-plugin --skill catalyst-appsailgit clone --depth 1 https://github.com/catalystbyzoho/claude-pluginWrote 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/catalystbyzoho/claude-plugin/catalyst-appsail)<a href="https://agentmods.dev/skills/catalystbyzoho/claude-plugin/catalyst-appsail"><img src="https://agentmods.dev/badge/skills/catalystbyzoho/claude-plugin/catalyst-appsail.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.00095 | $0.00597 |
| Opus 5 | $0.00048 | $0.00298 |
| Sonnet 5 | $0.00019 | $0.00119 |
| Haiku 4.5 | $0.00010 | $0.00060 |
Grade A, and why
catalyst-appsail 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 4d 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.
What it actually says
How It Works
-
Identify the runtime — Managed runtime (Node.js, Java, Python) or custom Docker container.
-
Load
references/appsail-basics.md— for PORT config, environment variables, Dockerfile requirements, and deploy commands. -
PORT rule — Always use
process.env.X_ZOHO_CATALYST_LISTEN_PORT, never hardcodePORTor3000. -
Serve & test locally, THEN deploy (local-first). Before
catalyst deploy appsail, runcatalyst serveand exercise the app's routes on Local (managed-service calls proxy to the Development environment), and run the project's test suite. Iterate locally until it passes; only then deploy to Development (catalyst deploy appsail --name <name> -ni), verify on the Development URL, and promote to Production only after that. Full loop:../catalyst-basics/references/project-basics.md→ Environments. -
AppSail vs Functions decision — If the user is unsure which to use, apply this matrix:
Catalyst Functions AppSail Code structure Catalyst-specific templates required Any framework, any format, fully independent Use case HTTP handlers, events, cron, Zoho integrations Persistent servers, long-running processes, Docker Billing Per API call Per instance uptime Dependency management Handled by Catalyst You manage all libraries and frameworks
Triggers
Use this skill for: "AppSail", "persistent server", "Docker on Catalyst", "backend hosting", X_ZOHO_CATALYST_LISTEN_PORT, appsail:add, "catalyst managed runtime", "deploy Express app", "AppSail vs Functions", "long-running process on Catalyst", or "containerized app on Catalyst".
References
| Reference | Load when the query is about… |
|---|---|
references/appsail-basics.md |
Runtimes, Docker setup, PORT env var, env variables, deploy commands, AppSail vs Functions decision table |
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.
- 4d ago First seen · 33 lines · 95 tokens per session scan A 24f0138f59b8
catalyst-appsail is a skill published in the GitHub repository catalystbyzoho/claude-plugin (0 stars, last pushed 22d ago), licensed Apache-2.0. It adds 95 tokens to every session and 597 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
kubernetes-specialist
Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies…
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
windows-builder
Build Windows images with Packer using WinRM communicator and PowerShell provisioners. Use when creating Windows AMIs, Azure images, or VMware templates.
deployment
Deploy Memoria with Docker Compose or Kubernetes. Environment variables, multi-instance setup, security. Use when deploying or configuring Memoria.
nvcf-self-managed-prerequisite
Install the prerequisites the NVCA operator / compute plane needs before nvcf-nvca-install can succeed: the operator tool nvcf-cli (required by the compute-plane stack's register-cluster step), KAI Scheduler (for the KAIScheduler feature gate), and the SMB CSI driver (for the sharedStorage Samba sidecar PVCs). The two…