Kimaki is a Discord-based orchestrator for OpenCode, an AI coding agent that edits files on a user's machine. It maps each project to a Discord channel and each coding session to a thread, allowing users to start, resume, search, and fork work through conversations. Catalogue add-ons provide Kimaki-related workflows for coding agents.
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 skills add remorses/kimaki --skill kimaki-tunnelgit clone --depth 1 https://github.com/remorses/kimakiWrote 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/remorses/kimaki/kimaki-tunnel)<a href="https://agentmods.dev/skills/remorses/kimaki/kimaki-tunnel"><img src="https://agentmods.dev/badge/skills/remorses/kimaki/kimaki-tunnel/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.
<a href="https://agentmods.dev/skills/remorses/kimaki/kimaki-tunnel"><img src="https://agentmods.dev/badge/skills/remorses/kimaki/kimaki-tunnel.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00083 | $0.00594 |
| Opus 5.5 | $0.00033 | $0.00238 |
| Sonnet 5.5 | $0.00017 | $0.00119 |
| Haiku 4.5 | $0.00008 | $0.00059 |
Grade A, and why
kimaki-tunnel 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 today.
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
Dev servers with tunnel access
Localhost URLs are useless from Discord. Wrap the dev server in kimaki tunnel to get a public URL, and run it in a named background tuistory session so you can wait for output, read logs and stop it later. Name the session descriptively (e.g. projectname-dev) and reuse it. Run tuistory --help first (or bunx tuistory when it is not installed). Invoke kimaki directly, not via npx or bunx.
- Use random tunnel IDs by default. Pass
-t <id>only for services that are safe to be publicly discoverable. kimaki tunneldetects the local port from the child output. Pass--portonly when the server prints no detectable localhost URL or port line.kimaki tunnelinjectsTRAFORO_URLinto the child process. Wire the app to it so OAuth callbacks, webhook URLs and absolute links use the public URL.
# start in a named background session, wait for output, then read the tunnel URL
tuistory launch "kimaki tunnel -- pnpm dev" -s myapp-dev
tuistory -s myapp-dev wait "/ready|local|tunnel/i" --timeout 30000
tuistory read -s myapp-dev
# pass the public URL to the app (better-auth, Next.js, Vite; node reads process.env.TRAFORO_URL)
tuistory launch "kimaki tunnel -- sh -c 'BETTER_AUTH_URL=$TRAFORO_URL exec pnpm dev'" -s myapp-dev
tuistory launch "kimaki tunnel -- sh -c 'APP_URL=$TRAFORO_URL exec pnpm dev'" -s myapp-dev
tuistory launch "kimaki tunnel -- sh -c 'VITE_BASE_URL=$TRAFORO_URL exec pnpm dev'" -s myapp-dev
# custom tunnel ID (only for intentionally public-safe services)
tuistory launch "kimaki tunnel -t holocron -- pnpm dev" -s holocron-dev
# list sessions; stop with Ctrl+C, then close
tuistory sessions
tuistory -s myapp-dev press ctrl c
tuistory -s myapp-dev close
Share the printed public URL with the user as a clickable link. Stop the session when the user is done.
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.
- today First seen · 35 lines · 83 tokens per session scan A 9fb630692174
kimaki-tunnel is a skill published in the GitHub repository remorses/kimaki (1,432 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 594 once invoked, about $0.0003 per session on Opus 5.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-10-16.
Other skills, from other repositories
horizon-cloud
Inspect Horizon cloud offers and companions, read or act on the cloud list of your workspace, see or propose changes to its Upkeep of Dependabot pull requests, control explicitly authorized companion workers, use a worker Local Network Bridge, or ask for GitHub access from a cloud worker through public MCP tools.
cmux-cloud-vm
Operate cmux Cloud machines, run durable remote commands or agents, and present their workspaces or services. Use for cmux vm/cloud tasks; backend implementation belongs to cmux-backend.
kubernetes
Deploy, manage, and debug Kubernetes in production — Deployments, Services, Gateway API, Service Mesh (Istio/Linkerd/Cilium), eBPF observability (Cilium Hubble), security hardening (Pod Security Standards, OPA/Kyverno, seccomp, runtime security with Falco/Tetragon), Helm, HPA, PDB, topology spread, and debugging. Use…
daytona-dev
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.
daytona-cloud-server
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
mount
Use this whenever the user asks to mount anything — local folders, S3 buckets, S3-compatible services (Cloudflare R2, MinIO), or Adobe da.live / AEM Document Authoring repos. Read this skill BEFORE deciding which backend to use; do NOT default to a local file picker when the user names a remote service. Covers…