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-debuggit 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-debug)<a href="https://agentmods.dev/skills/remorses/kimaki/kimaki-debug"><img src="https://agentmods.dev/badge/skills/remorses/kimaki/kimaki-debug/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-debug"><img src="https://agentmods.dev/badge/skills/remorses/kimaki/kimaki-debug.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.00095 | $0.00758 |
| Opus 5.5 | $0.00038 | $0.00303 |
| Sonnet 5.5 | $0.00019 | $0.00152 |
| Haiku 4.5 | $0.00010 | $0.00076 |
Grade A, and why
kimaki-debug 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging Kimaki
Read the logs before guessing. Do not restart the bot (kimaki restart) unless the user explicitly asks.
Kimaki bot log
$KIMAKI_DATA_DIR/kimaki.log holds only the current bot run. The run before the last restart (with the crash that caused it) is in kimaki.previous.log. Lines are <ISO time> <LEVEL> [<MODULE>] <message> and errors include their cause chain. It logs incoming messages, run start/finish/failure per thread and session, Discord and OpenCode errors, routines and crashes.
tail -n 200 $KIMAKI_DATA_DIR/kimaki.log
grep -E ' (WARN|ERROR) ' $KIMAKI_DATA_DIR/kimaki.log | tail -n 50
grep '<thread_id or ses_id>' $KIMAKI_DATA_DIR/kimaki.log
OpenCode service log
The shared opencode serve --service daemon appends to ~/.local/share/opencode/log/opencode.log ($XDG_DATA_HOME/opencode/log; opencode debug paths prints the folder). The file is never reset and can be very large: use tail or grep, never read it whole. Lines are logfmt. run=<id> is one daemon process, so filter by the run of the last line. The daemon pid and URL are in ~/.local/state/opencode/service.json.
LOG=~/.local/share/opencode/log/opencode.log
RUN=$(tail -n 1 $LOG | grep -o 'run=[a-z0-9]*')
grep "$RUN " $LOG | grep -E '^timestamp=[^ ]+ level=(ERROR|WARN)' | tail -n 50
grep "$RUN " $LOG | grep '<ses_id>' | tail -n 100
Other tools
kimaki session events <id>prints the recorded OpenCode events of a thread as JSONL.kimaki restartrestarts the bot (only when asked). Sessions keep running in OpenCode.kimaki profile cpu --duration 30sandkimaki profile heapprint the profile file path.kimaki login PROVIDERlists login methods of a provider.--keyconnects an API key,--methodstarts OAuth,--attemptchecks or completes an attempt. Credentials belong to OpenCode.
Who can use the bot
Only users with one of these Discord permissions can message the bot: Server Owner, Administrator, Manage Server, or the "Kimaki" role (case-insensitive). Other Discord bots are ignored; assign a bot the "Kimaki" role to let it trigger sessions (multi-agent orchestration).
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 · 45 lines · 95 tokens per session scan A 7365782f4a13
kimaki-debug is a skill published in the GitHub repository remorses/kimaki (1,432 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 758 once invoked, about $0.0004 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
simplify-codebase
Simplification audit or authorized codebase simplification whose stated objective is to remove accidental complexity. Use for evidence-backed deletion or consolidation of dead code, duplicate state, redundant APIs or layers, ownerless abstractions, obsolete compatibility or design records, and over-engineering in any…
trace
Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode.
ai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode.
debug
Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction.
verify
Verify that a change really works before you claim completion.
horizon-speech
Check that a microphone is usable for Horizon dictation and report which layer is at fault — no signal, bad level, or a genuine model/accent limit. Use when dictation produces wrong, unrelated, or empty text.