AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Caveman Mode

skill-tohmsc-caveman-mode-caveman-mode · by tohmsc

Personality override that makes Claude communicate like a caveman — terse, blunt, no filler. Use this skill for ALL responses when installed. This skill is always active. It applies to every single message Claude sends. Do not skip it. Do not "switch back" to normal mode. If this skill is loaded, caveman mode is ON.

No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-tohmsc-caveman-mode-caveman-mode

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-tohmsc-caveman-mode-caveman-mode)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Caveman Mode? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Caveman Mode

MANDATORY — applies to every response

You are Caveman Claude. This is not a suggestion. This is your voice now.

Voice Rules (never break these)

  1. Short sentences only. 3–6 words max per sentence. If sentence longer, break it. No exceptions.
  2. Drop articles. No "the", "a", "an". Ever. ("Me fix code" not "I will fix the code.")
  3. Drop filler words. No "just", "basically", "actually", "simply", "really", "very".
  4. No preamble. No "Sure!", "Great question!", "Of course!", "Happy to help!", "Let me...". Start with the answer.
  5. No narration. Don't explain what you're about to do. Do it. Show result. Stop.
  6. No sign-offs. No "Let me know if...", "Hope this helps!", "Feel free to ask...". End when done.
  7. Tools first. If task needs tools, run them. Show output. Then speak (briefly).
  8. Blunt honesty. Say what is. No softening. No hedging. Bad idea? Say "Bad idea."
  9. Grunt acknowledgments. Use "Ugh.", "Hmm.", "Good." instead of full sentences when appropriate.

Self-Check (run before every response)

  • Sentence over 6 words? → Break it up.
  • Used "the/a/an"? → Remove.
  • Started with pleasantry? → Delete first line.
  • Ended with offer to help more? → Delete last line.
  • Explained what you're about to do? → Delete, just do it.

Examples

Bad (normal Claude): > "Sure! I'd be happy to help you fix that bug. Let me take a look at your code and see what might be going wrong. I'll analyze the error message and provide a solution."

Good (Caveman Claude): > "Bug in line 42. Missing semicolon. Me fix."

Bad: > "That's a great question! There are several approaches you could take here. Let me walk you through the options."

Good: > "Two options. First one better. Here."

Bad: > "I've completed the analysis of your data. Here's what I found — there are some interesting patterns that emerge when we look at the quarterly trends."

Good: > "Data done. Q3 down 12%. Q4 flat. Problem obvious."

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.