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 rules/usekaneo/kaneo/deployment-devopsgit clone --depth 1 https://github.com/usekaneo/kaneoWhat 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.00000 | $0.02159 |
| Opus 5 | $0.00000 | $0.01079 |
| Sonnet 5 | $0.00000 | $0.00432 |
| Haiku 4.5 | $0.00000 | $0.00216 |
Grade A, and why
deployment-devops 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 — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment & DevOps Guidelines
Kaneo supports multiple deployment methods: Docker Compose for development/testing and Kubernetes for production. This document outlines deployment patterns and best practices.
Docker Compose
Configuration
The main Docker Compose configuration is in compose.yml at the project root.
Service Structure
services:
postgres:
image: postgres:16-alpine
env_file:
- .env
ports:
- "5432:5432"
volumes:
- postgres_data:/var/lib/postgresql/data
restart: unless-stopped
healthcheck:
test: ["CMD-SHELL", "pg_isready -U kaneo -d kaneo"]
interval: 10s
timeout: 5s
retries: 5
api:
image: ghcr.io/usekaneo/api:latest
ports:
- "1337:1337"
env_file:
- .env
depends_on:
postgres:
condition: service_healthy
restart: unless-stopped
web:
image: ghcr.io/usekaneo/web:latest
ports:
- "5173:5173"
env_file:
- .env
depends_on:
- api
restart: unless-stopped
Best Practices
- Health Checks: Always include health checks for databases
- Dependencies: Use
depends_onwithcondition: service_healthyfor databases - Volumes: Use named volumes for persistent data
- Restart Policy: Use
unless-stoppedfor production-like behavior - Environment Variables: Use
.envfile, never hardcode secrets
# Good: Proper health check and dependency
services:
api:
depends_on:
postgres:
condition: service_healthy
postgres:
healthcheck:
test: ["CMD-SHELL", "pg_isready -U kaneo -d kaneo"]
interval: 10s
timeout: 5s
retries: 5
Kubernetes (Helm Charts)
Chart Structure
Helm charts are located in charts/kaneo/:
charts/kaneo/
├── Chart.yaml # Chart metadata
├── values.yaml # Default values
├── README.md # Chart documentation
└── templates/
├── deployment.yaml # API and Web deployments
├── services.yaml # Service definitions
├── ingress.yaml # Ingress configuration
├── postgresql-deployment.yaml # PostgreSQL deployment
├── pvc.yaml # Persistent volume claims
├── hpa.yaml # Horizontal Pod Autoscaler
└── serviceaccount.yaml # Service accounts
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 · 415 lines · 0 tokens per session scan A abb56273517a
deployment-devops is a cursor rule published in the GitHub repository usekaneo/kaneo (8,786 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,159 tokens. 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 cursor rules, from other repositories
no-co-author-in-commits
Do not add or keep Co-authored-by trailers in commit messages.
no-mvn-compile
Do not run mvn compile; rely on IDE lint errors.
git-and-monorepo
Commit message convention and pnpm/Nx monorepo rules.
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
clawsweeper
Triage and process the Slate v2 issue ledger with OpenClaw-style sweep discipline: archive-first discovery, duplicate proof, small-fix gates, exact claim rules, maintainer-safe issue output, and gitcrawl API refreshes.
slate-ar-status
Read-only status shortcut for Slate v2 Autoresearch. Shows current session state, dashboard URL, next recommended action, blockers, and latest metric evidence without running packets or editing files.