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/ssube/conclave/conclave-buildnpx skills add ssube/conclave --skill conclave-buildgit clone --depth 1 https://github.com/ssube/conclaveWrote 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/ssube/conclave/conclave-build)<a href="https://agentmods.dev/skills/ssube/conclave/conclave-build"><img src="https://agentmods.dev/badge/skills/ssube/conclave/conclave-build.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.00045 | $0.02148 |
| Opus 5 | $0.00023 | $0.01074 |
| Sonnet 5 | $0.00009 | $0.00430 |
| Haiku 4.5 | $0.00005 | $0.00215 |
Grade B, and why
conclave-build scanned grade B with 1 finding 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 3d 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.
6. Verify specific changes: `sudo nerdctl exec conclave-dev <command>` How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conclave Build
Build and test the Conclave all-in-one container locally using scripts/dev.sh.
Quick Reference
# Full cycle: build image + start container + run tests
bash scripts/dev.sh
# Individual steps
bash scripts/dev.sh build # build the image only
bash scripts/dev.sh run # start container (runs tests automatically)
bash scripts/dev.sh test # run browser tests against running container
bash scripts/dev.sh stop # stop and remove container
bash scripts/dev.sh clean # stop container AND delete the workspace volume
bash scripts/dev.sh logs # tail container logs
bash scripts/dev.sh creds # print admin and agent passwords
Build Process
The Dockerfile builds in this order:
- Base image:
nvidia/cuda:12.4.1-runtime-ubuntu22.04 - Copy into image:
ansible/,configs/,dashboard/,pi/ - Run Ansible playbook: installs all services (postgres, nginx, synapse, chromadb, ollama, planka, neko, ttyd, chromium, coding agents)
- Copy scripts:
scripts/copied to/opt/conclave/scripts/ - Entrypoint:
scripts/startup.sh
Container Runtime
All services run under supervisord (configs/supervisord.conf). Key programs:
| Priority | Service | Port |
|---|---|---|
| 10 | postgres, nginx, sshd, cron | 5432, 8888, 22, — |
| 14-17 | dbus, xvfb, pulseaudio, openbox, chromium | 9222 (internal) |
| 30 | synapse, chromadb, ollama, ttyd, pushgateway | 8008, 8000, 11434, 7681, 9091 |
| 40 | planka | 1337 |
| 50 | neko | 8080, 8081 (TCPMUX) |
| 99 | tmux-session, ollama-pull, create-users | oneshot |
First Boot Flow
startup.sh runs on every container start:
- Generate secrets (passwords, tokens) if first boot
- Render config templates (nginx, element-web, planka, chromadb, neko)
- Write
agent-env.shwith credentials for coding agents - Sync pi skills/extensions to
/workspace/data/coding/.pi/agent/ - Copy default
pi-settings.jsonandcron.tab - Launch supervisord
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.
- 3d ago First seen · 201 lines · 45 tokens per session scan B 95f0b1cc880f
conclave-build is a skill published in the GitHub repository ssube/conclave (2 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 2,148 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.
docker
Docker containerization, multi-stage builds, non-root security, layer caching optimization, and docker-compose standards.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.
k8s-security-policies
Comprehensive guide for implementing NetworkPolicy, PodSecurityPolicy, RBAC, and Pod Security Standards in Kubernetes.
kubernetes-expert
Expert Kubernetes: workloads, services, config, probes, resources, and troubleshooting. Trigger keywords: Kubernetes, k8s, Deployment, StatefulSet, Service, Pod, ConfigMap, Secret, Ingress, liveness, readiness, probe, requests, limits, HPA, kubectl, Helm, CrashLoopBackOff, ImagePullBackOff, OOMKilled. Use for writing…