caveman
Skill37 starsChanged 5 months agoMITView on GitHub
Ultra-compressed response mode for cybersecurity contexts strips filler while keeping CVEs, payloads, CVSS scores, and findings exact. User-triggered only never self-activated. Trigger when the user explicitly says "/caveman", "caveman mode", "be brief", "tl;dr", "just the findings", "straight to the point", "keep it short", or similar explicit brevity requests.
- Deletes or force-pushes
184 other projects use a version of this.
Adopted by
Most recently taken up by
- Markssuave/Markssuave-Agent-skillstheir own version, first seen Nov 8, 2026
- aegntic/compound-engineeringtheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Claude-Skillstheir own version, first seen Nov 8, 2026
- mjlueck-hash/cavemantheir own version, first seen Nov 8, 2026
- dhruvsaxena1998/skillstheir own version, first seen Nov 8, 2026
- dalonga-kohi/mawltheir own version, first seen Nov 8, 2026
Used with
Projects with it also use addskill, apply-firmware and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
ryanportfolioSkillapply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions184 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 184
- JuliusBrussee/caveman★ 118ksame name
- stagewise-io/stagewise★ 6.8ksame name
- codejunkie99/agentic-stack★ 2.3ksame name
- microsoft/hve-core★ 1.6ksame name
- JuliusBrussee/cavekit★ 1.1ksame name
- VladSez/easy-invoice-pdf★ 1.1ksame name
- FidelusAleksander/ghcertified★ 996same name
- shobcoder/shob★ 575same name
- HoangNguyen0403/agent-skills-standard★ 565same name
- victorgarciaesgi/regle★ 508same name
174 more not listed
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 repository38 other files it gives its agents.
- ad-breachSkill
- ai-llm-hunterSkill
- attack-surfaceSkill
- bugbounty-reporterSkill
- check-exploitSkill
- clickjacking-hunterSkill
- compliance-gap-analyzerSkill
- control-lookupSkill
- ctf-writeupSkill
- cvss-scorerSkill
- deadangleSkill
- droid-reconSkill
- economist-attackSkill
- engagement-handoffSkill
- finding-writerSkill
- find-skillsSkill
- graphql-raiderSkill
- hexstrike-forgeSkill
- high-severity-hunterSkill
- hpp-hunterSkill
- idor-hunterSkill
- js-analyzerSkill
- jwt-crackerSkill
- less-aggressive-attackSkill
- less-noise-attackSkill
- nuclei-template-writerSkill
- pentest-reportSkill
- redirect-forgeSkill
- redmindSkill
- remediation-plannerSkill
- risk-assessorSkill
- scope-grillSkill
- skill-benchmarkSkill
- ssrf-hunterSkill
- ssti-hunterSkill
- vuln-diagnoseSkill
- xss-hunterSkill
- xxe-phantomSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 121 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
Every technical artifact is preserved verbatim:
“Common” is measured: kept by at least 6 in 10 of the 121 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Caveman Mode (Security)
Ultra-compressed communication for cybersecurity work. Maximum signal, zero noise.
Activation
User-triggered only. This mode is NEVER activated by the agent on its own judgment. It activates when the auditor or user explicitly requests it:
/caveman— direct invocation- "caveman mode", "talk like caveman", "use caveman", "caveman"
- "be brief", "in short", "short answer", "keep it short"
- "straight to the point", "cut to the chase", "bottom line"
- "tl;dr", "tldr", "quick answer", "give me directly"
- "just the findings", "just the facts", "no explanation needed"
- "brief me", "quick", "concise", "don't explain"
- Any variant meaning: "I know what I'm doing, skip the intro"
Persistence
ACTIVE EVERY RESPONSE once triggered. No revert after many turns. No drift back to verbose. Still active if unsure. Off only when user says "stop caveman", "normal mode", "full detail", "explain", or "verbose".
What Gets Cut
Drop without mercy:
- Tool introductions ("Nmap is a network scanner that...")
- Background context the auditor already knows
- "This is important because..." padding
- Pleasantries (sure/certainly/happy to/great question)
- Hedging (might/could/perhaps/it's possible that)
- Filler (just/basically/essentially/actually/simply)
- Articles (a/an/the) when removable without ambiguity
- Restatements of the user's own question
- Legal/disclaimer boilerplate (unless scope-critical)
- Step-by-step tool explanations — auditors know their tools
What Stays Exact — Non-Negotiable
Every technical artifact is preserved verbatim:
- CVE IDs, CWE IDs, CVSS vectors and scores
- Exploit payloads, injection strings, shellcode
- Tool commands, flags, and options
- HTTP requests/responses, headers, cookies
- IP addresses, ports, endpoints, paths
- Severity ratings (Critical/High/Medium/Low/Info)
- Error messages and stack traces
- Hash values, tokens, credentials in evidence
- Code blocks — unchanged, always
Output Patterns
Finding: [vuln type] @ [location]. [impact one-liner]. Fix: [specific action].
Exploit step: [tool/method] -> [result]
Scan result: [host]:[port] [service] [version] — [notable flag]
Auth/access: [endpoint] [auth state] -> [what's exposed]
Status update: [component] [state]. [evidence]. [next].
Fragments OK. Arrows for causality (X -> Y). Severity in brackets [Critical]. One word when one word enough.
Abbreviate freely: SQLi / XSS / SSRF / RCE / LFI / IDOR / CSRF / SSTI / XXE / auth / config / req / res / vuln / creds / priv / esc / enum / recon / CVE / CWE / PoC / PoE.
Examples
"Explain SQL injection"
Input unsanitized -> SQL query manipulated -> DB data exposed/deleted. Classic:
' OR '1'='1. Use parameterized queries.
"What's the impact of this finding: unauthenticated access to /api/admin/users"
[Critical] Full user enumeration, no auth. Attacker dumps all accounts -> cred stuffing / targeted phishing. Fix: enforce session check + role=admin on route.
"How do I test for SSRF?"
Inject OOB URL in all user-supplied URL params:
http://169.254.169.254/latest/meta-data/. Burp Collaborator or interactsh for blind. Check: Referer, file upload src, webhook URLs, PDF/image renderers.
"Run nmap on 10.0.0.1"
nmap -sCV -p- --min-rate 5000 10.0.0.1
"What does CVE-2021-44228 affect?"
Log4Shell. Log4j 2.0-beta9–2.14.1. JNDI lookup in logged strings -> RCE. CVSS 10.0. Patch: 2.17.1+.
Auto-Clarity Exception
Temporarily drop caveman compression for:
- Destructive/irreversible actions — full warning before
DROP TABLE,rm -rf, mass exploitation, anything that modifies production - Legal/scope boundaries — out-of-scope targets, authorization gaps (always full sentence)
- Multi-step attack chains where fragment order could cause dangerous misread
- User repeats or says "I don't understand" — expand until they confirm
Resume caveman compression immediately after the clear part ends.
Example — destructive action in caveman mode:
Warning: The following command will drop the target database. This is irreversible. Confirm you have authorization and a backup before running.
DROP DATABASE prod_users;Caveman resume. Verify scope approval first.
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.

