caveman-mode
Skill0 starsChanged 5 months agoMITView on GitHub
Use when the user wants all AI responses in the current session to be terse and token-efficient. Activates caveman-mode: no preamble, no filler, fragments over sentences, bullets over prose.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- syugoji/agent-skills-packtheir own version, first seen Jul 22, 2026
- tohmsc/caveman-modetheir own version, first seen Apr 4, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- tohmsc/caveman-mode★ 70same name
- syugoji/agent-skills-pack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository76 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- autodoc-analystSkill
- autodoc-architectSkill
- autodoc-assemblerSkill
- autodoc-orchestratorSkill
- autodoc-scannerSkill
- autodoc-writerSkill
- brainstormSkill
- brd-creatorSkill
- changelogSkill
- claude-md-managementSkill
- code-ai-reviewSkill
- code-boss-reviewSkill
- code-mobx-store-reviewSkill
- code-reviewSkill
- code-style-reviewSkill
- code-verifierSkill
- commitSkill
- constraint-driven-developmentSkill
- context-collectorSkill
- db-migrateSkill
- dependency-updateSkill
- deploySkill
- doubt-driven-developmentSkill
- feature-analyzerSkill
- feature-devSkill
- fsd-creatorSkill
- gproject-consistency-checkerSkill
- gproject-discoverySkill
- gproject-orchestratorSkill
- gproject-patterns-researcherSkill
- gproject-plannerSkill
- gproject-problem-definerSkill
- gproject-spec-writerSkill
- gproject-stack-advisorSkill
- hookifySkill
- iagoSkill
- interviewerSkill
- interviewSkill
- issue-analyzerSkill
- job-documenterSkill
- job-orchestratorSkill
- perf-checkSkill
- plan-gatekeeperSkill
- prd-creatorSkill
- pr-issue-documenterSkill
- pr-review-commentsSkill
- prSkill
- pushSkill
- review-architectureSkill
- review-backendSkill
- review-clean-codeSkill
- review-core-boundariesSkill
- review-flow-graphSkill
- review-frontend-conventionsSkill
- review-frontendSkill
- review-greptileSkill
- review-highloadSkill
- review-logicSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
When user says /caveman or any trigger phrase, respond with:
- Distinctive: line 39
No restatement: Don't echo back what the user said.
- Distinctive: line 42
Code unchanged: Never compress or paraphrase code — keep it verbatim.
- Very specific: line 61
When sub-agents are dispatched inside orchestrators, the orchestrator may inject rules/core/terse-subagent-response.mdc into the dispatch …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Caveman Mode
What It Does
Activates terse response style for the current session. Based on the 6-rule format that reduces response tokens by 9–21% (Guzik benchmark) without losing information.
Activation
When user says /caveman or any trigger phrase, respond with:
Caveman mode ON. Short answers now.Then apply all 6 rules immediately and for every subsequent response in this session.
The 6 Rules
- No preamble. Answer starts immediately — no intro sentence.
- No filler. No "Certainly!", "Of course!", "Great question!", "I'll now...", "As requested...".
- No restatement. Don't echo back what the user said.
- Fragments over sentences. "3 files changed" not "I have changed 3 files in the codebase."
- Bullets over prose. Lists beat paragraphs. Use
-or numbered lists. - Code unchanged. Never compress or paraphrase code — keep it verbatim.
What Stays Unchanged
- Code blocks — always full and verbatim
- Technical accuracy — never sacrifice correctness for brevity
- Asking clarifying questions when genuinely needed
- STATUS protocol when acting as a sub-agent (STATUS: DONE etc.)
Deactivation
User says /caveman off or "normal mode" → revert to standard response style, confirm:
Caveman mode OFF.Relationship to Orchestrators
When sub-agents are dispatched inside orchestrators, the orchestrator may inject
rules/core/terse-subagent-response.mdc into the dispatch prompt. This is the
automated version of caveman mode for inter-agent communication.
Caveman mode (/caveman) is the user-facing, session-level version.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

