caveman-learn
Reduce Agent Token Usage
Large configuration files and repeated context increase token usage. This skill reviews Caveman reports and applies measured changes with individual approval.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "caveman-learn" from https://skillstore.io/skills/juliusbrussee-caveman-learn.md and its manifest at https://skillstore.io/api/skills/juliusbrussee-caveman-learn/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "caveman-learn". Review my report without editing anything.
Expected outcome:
Cave Score: 72. The largest reducible sink is project instructions. Recurring context ranks second. Load-bearing guidance remains unchanged.
Using "caveman-learn". Propose a safe offload for the repeated deployment notes.
Expected outcome:
- Source hash matches the report locator.
- The compact pointer and recall cost are lower than repeated loading.
- Approve storing the block and replacing it with the proposed recall pointer?
Using "caveman-learn". Apply the approved trim.
Expected outcome:
The approved section was trimmed. Tokens per turn decreased from 420 to 285. The original content and reversal steps are recorded.
Security Audit
SafeAll 17 static findings are false positives caused by documentation paths, Markdown backticks, test assertions, or bounded Caveman file access. The skill requires consent, integrity checks, measurement, and rollback before changing user configuration.
Risk Factors
📁 Filesystem access (12)
⚙️ External commands (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/juliusbrussee-caveman-learn/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/juliusbrussee-caveman-learn?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/juliusbrussee-caveman-learn?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/juliusbrussee-caveman-learn/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/juliusbrussee-caveman-learn.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
juliusbrussee. (2026). caveman-learn security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/juliusbrussee-caveman-learn/audits/1BibTeX citation
@techreport{juliusbrussee-juliusbrussee-caveman-learn-2026,
author = {juliusbrussee},
title = {caveman-learn security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/juliusbrussee-caveman-learn/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "caveman-learn security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "juliusbrussee"
date-released: "2026-08-12"
url: "https://skillstore.io/skills/juliusbrussee-caveman-learn/audits/1"
identifiers:
- type: other
value: "skillstore:juliusbrussee-caveman-learn:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Trim project instructions
Review a large CLAUDE.md and approve only edits that reduce measured tokens per turn.
Offload recurring context
Move repeated session context into cavemem while preserving compact recall and exact recovery paths.
Review team token usage
Present ranked token sinks and separate actionable configuration findings from load-bearing context.
Try These Prompts
Run my Caveman learn report and explain the ranked token sinks without changing files.
Review reducible findings, show each proposed diff and measured impact, then ask before every edit.
Find recurring context suitable for cavemem, verify its hash, measure recall cost, and propose a reversible offload.
Process only my selected sinks, preserve load-bearing content, validate every recall path, and revert changes without confirmed token reduction.
Best Practices
- Review the complete report before selecting changes.
- Approve each diff only after checking its measured impact.
- Test recall and exact recovery before accepting an offload.
Avoid
- Do not apply every recommendation without reviewing individual diffs.
- Do not remove load-bearing instructions to improve the score.
- Do not keep changes that fail to reduce tokens or preserve recall.
Frequently Asked Questions
Does this skill edit files automatically?
What is a reducible finding?
What is recurring context?
How does cavemem offloading stay reversible?
Will it change load-bearing content?
How are savings validated?
Developer Details
Author
juliusbrusseeLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
663bc75480aaf8c7b857fb3b51c35654a097de3d
Maintenance freshness
8/13/2026
Usage
0 downloads · 0 views
File structure