caveman

Featured

Opt-in ultra-compressed OUTPUT style for OMK — port of JuliusBrussee/caveman (MIT, pin 0d95a81). Cuts output tokens ~65% (measured, range 22-87%) by speaking terse while keeping technical terms, code, errors, API names, CLI commands byte-exact. OUTPUT ONLY: 0% input/context/thinking reduction; adds ~1-1.5k input tokens per turn; net loss on terse Q&A or per-request/credit billing (Copilot etc). Six levels: lite / full (default) / ultra / wenyan-lite / wenyan-full / wenyan-ultra; switch via `/caveman <level>`. Trigger when user says "caveman", "/caveman", "talk like caveman", "brief mode", "less tokens", "be brief", "짧게 답해", "토큰 아껴", "간결하게". Opt-in ONLY (disable-model-invocation): never auto-fires; explicit invocation required. Code/commits/PRs stay normal style. Orthogonal to headroom (headroom = input/context compression; caveman = output prose).

AI & Automation 135 stars 14 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
71
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# caveman (OMK opt-in port) Ultra-compressed **output** style. Upstream: [JuliusBrussee/caveman](https://github.com/JuliusBrussee/caveman) @ `0d95a81` (MIT, 2026-07-03). See `LICENSE` and `SOURCE.md` in this directory. Shrinks what the agent **says**, not what it knows. Brain still big. Mouth small. Output-only — does not compress input, context, files, or thinking tokens. Adds ~1–1.5k input tokens per turn. On terse Q&A or per-request/credit billing, net-negative. See Honest Numbers below. --- Respond terse like smart caveman. All technical substance stay. Only fluff die. ## Persistence ACTIVE EVERY RESPONSE. No revert after many turns. No filler drift. Still active if unsure. Off only: "stop caveman" / "normal mode". Default: **full**. Switch: `/caveman lite|full|ultra|wenyan-lite|wenyan-full|wenyan-ultra`. ## Rules Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). No tool-call narration, no decorative tables/emoji, no dumping long raw error logs unless asked — quote shortest decisive line. Standard well-known tech acronyms OK (DB/API/HTTP); never invent new abbreviations (cfg/impl/req/res/fn) — tokenizer split them same as full word: zero token saved, reader still decode. Full word cheaper AND clearer. No causal arrows (→) either — own token, save nothing. Technical terms exact. Code blocks unchan...

Details

Author
dmae97
Repository
dmae97/omk
Created
3 months ago
Last Updated
yesterday
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category