kodus-installer: Skill for Claude Code

.claude/skills/kodus-install/SKILL.md

kodus-install is a skill for Claude Code from kodustech/kodus-installer. It costs 32 tokens per session (2,027 once invoked), scanned A, original, MIT.

A guided installer for running Kodus, a self-hosted service, with Docker Compose, a tool for defining and starting multiple containers together. It checks prerequisites, prepares configuration, starts the services, and verifies their health.

In plain words
What is it for?
Use it to check the local Docker setup, create or review a .env configuration file, generate secrets, start Kodus, and confirm that the services are healthy.
Why use it?
It reduces the chance of missing Docker, configuration, secrets, or startup checks during installation. It also pauses before changing the environment file or running installation scripts.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

This is kodustech/kodus-installer's own configuration. It tells Claude Code how to work on kodus-installer itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kodus-installer configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash scripts/generate-secrets.sh.

Reuse

Borrowing it

Nothing to install: this file belongs to kodustech/kodus-installer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kodustech/kodus-installer/main/.claude/skills/kodus-install/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/kodustech/kodus-installer

Made for: Claude Code.

Wrote 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.

agentmods badge for kodus-install

README.md
[![agentmods](https://agentmods.dev/badge/skills/kodustech/kodus-installer/kodus-install/github.svg)](https://agentmods.dev/skills/kodustech/kodus-installer/kodus-install)
Your own site
<a href="https://agentmods.dev/skills/kodustech/kodus-installer/kodus-install"><img src="https://agentmods.dev/badge/skills/kodustech/kodus-installer/kodus-install/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.

agentmods 80×15 button for kodus-install

Your own site · 80×15
<a href="https://agentmods.dev/skills/kodustech/kodus-installer/kodus-install"><img src="https://agentmods.dev/badge/skills/kodustech/kodus-installer/kodus-install.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,027 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 4 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 3
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Privilege Escalation · line 8
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Privilege Escalation · line 23
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • medium Data Exfiltration · line 112
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.02027
Opus 5 $0.00016 $0.01014
Sonnet 5 $0.00006 $0.00405
Haiku 4.5 $0.00003 $0.00203

Measured 9d ago against content hash 1cd791f112e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

kodus-install 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 9d 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.

.claude/skills/kodus-install/SKILL.md · 195 lines

How it starts

The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are helping the user install Kodus self-hosted. Follow each phase in order. Be conversational but concise. Always confirm before writing to .env or running scripts.

Phase 1 — Prerequisites

Run the following checks before anything else:

  1. Check Docker is installed: docker --version
  2. Check Docker daemon is running: docker info
  3. Check Docker Compose is available: docker compose version (fall back to docker-compose version)
  4. Confirm the current working directory contains docker-compose.yml and scripts/install.sh. If not, tell the user to cd into the kodus-installer directory and stop.

If any prerequisite fails, explain what is missing and stop. Do not proceed until all pass.


Phase 2 — .env Setup

Check if .env exists in the current directory.

If .env does not exist:

  • Copy .env.example to .env: cp .env.example .env
  • Tell the user you're starting fresh from the example file.

If .env already exists:

  • Ask the user: do they want to (a) keep existing config and go straight to install, or (b) review and update the config?
  • If they choose (a), skip to Phase 5.

Phase 3 — Configuration Walkthrough

Read the current .env file, then go through each section below. For each variable, check if it already has a non-empty value. If it does, show the current value and ask if they want to keep it or change it. If it is empty, ask for the value.

Use Edit to update variables in .env as the user provides answers. Never rewrite the whole file — only edit specific lines.

3.1 — Basic Settings

Variable Description Default
WEB_PORT Port for the Kodus web UI 3000
API_WEBHOOKS_PORT Port for the webhooks service 3332
NEXTAUTH_URL Full URL where users will access Kodus (e.g. http://localhost:3000 or https://kodus.yourdomain.com)
WEB_HOSTNAME_API Hostname only (no scheme, no path) where the API is reachable from Git providers for webhooks (e.g. api.yourdomain.com). If running locally without public access, use localhost.

Read the full file on GitHub · 195 lines

Changes

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.

  1. 9d ago First seen · 195 lines · 32 tokens per session scan A 1cd791f112e6

Subscribe to this mod's changes

kodus-install is a skill published in the GitHub repository kodustech/kodus-installer (11 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 2,027 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

github-actions-templates

Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.

wshobson/agents · 44 tokens

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…

omnigent-ai/omnigent · 84 tokens

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…

microsoft/skills · 166 tokens

azure-cloud-migrate

Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…

microsoft/skills · 106 tokens

azure-kubernetes-app-deploy

Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster…

microsoft/skills · 166 tokens

observal

Operates the Observal CLI for authentication, configuration, setup diagnosis, teamspaces, inbox work, scans, update checks, and authenticated API access. Use when the user wants to log in, configure Observal, inspect local harness setup, manage a teamspace or invitation, process inbox items, check installed registry…

Observal/Observal · 79 tokens