Agent Cost Report
Believable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices…
Map what the owner wants from the prompts they typed themselves (prompts an agent wrote are left out), then sort it into focus areas, asks and rules, each with dated quotes, and save them to My Work (areas as My Focus suggestions, rules as My Rules suggestions). Use when asked for "owner goals", "my goals", "what do I want", "what am I asking for", "map my prompts", or to refresh Goals in My Work.
This skill is part of the claude-mem plugin and uses its shared scripts and agents. Install the whole plugin by typing these in Claude Code:
> /plugin marketplace add thedotmack/claude-mem> /plugin install claude-mem@thedotmackThe first command adds the publisher's marketplace, the second installs the plugin. Start a new session if the skills don't show up straight away.
Once it's installed, Claude reads this skill on its own whenever a request matches what it's for, so you don't have to mention it by name. In Claude Code you can also run it directly by typing /owner-goals.
It includes scripts that Claude may run on your computer, so skim them on GitHub before you install. It is part of the claude-mem plugin and uses that plugin's shared scripts and agents, so install the whole plugin for the best results.
Section headings from the skill's SKILL.md file.
Believable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices…
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are…
Set up, check, or restore local claude-mem database snapshots. Use when the user says "set up backups", "back up my memories", "backup status", or "restore my database".
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it…
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop…