what-did-i-get-done

what-did-i-get-done is a skill for Claude Code from michael-denyer/pstack-claude. It costs 24 tokens per session (222 once invoked), scanned A, original, MIT.

A tool for summarizing code commits written by the current Git user during a chosen time period. Git commits are saved records of changes made to a codebase.

In plain words
What is it for?
Use it to prepare concise updates covering work completed yesterday, over several days, or during the previous week.
Why use it?
It turns a commit history into a short status update without mixing in uncommitted work or inferring reasons for changes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pstack plugin — 56 skills, 2 agents, 1 hook shipped together

Good fit Use it to prepare concise updates covering work completed yesterday, over several days, or during the previous week.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/michael-denyer/pstack-claude/what-did-i-get-done
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add michael-denyer/pstack-claude --skill what-did-i-get-done
Clone the repo
git clone --depth 1 https://github.com/michael-denyer/pstack-claude

Made for: Claude Code.

Or install pstack, the plugin that ships this one along with the rest of its 56 skills, 2 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for what-did-i-get-done

README.md
[![agentmods](https://agentmods.dev/badge/skills/michael-denyer/pstack-claude/what-did-i-get-done/github.svg)](https://agentmods.dev/skills/michael-denyer/pstack-claude/what-did-i-get-done)
Your own site
<a href="https://agentmods.dev/skills/michael-denyer/pstack-claude/what-did-i-get-done"><img src="https://agentmods.dev/badge/skills/michael-denyer/pstack-claude/what-did-i-get-done/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for what-did-i-get-done

Your own site · 80×15
<a href="https://agentmods.dev/skills/michael-denyer/pstack-claude/what-did-i-get-done"><img src="https://agentmods.dev/badge/skills/michael-denyer/pstack-claude/what-did-i-get-done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 222 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00222
Opus 5 $0.00012 $0.00111
Sonnet 5 $0.00005 $0.00044
Haiku 4.5 $0.00002 $0.00022

Measured yesterday against content hash 479813c9abaa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

what-did-i-get-done scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

plugins/pstack/skills/what-did-i-get-done/SKILL.md · 32 lines

What it actually says

What did I get done

Trigger

Need a short, high-signal summary of work completed in a specific time range (for example: yesterday, last 3 days, or last week).

Workflow

  1. Resolve the requested time window into concrete dates.
  2. Read commits authored by the current git user email within that range.
  3. Exclude merge commits and uncommitted changes.
  4. Synthesize the most important shipped changes into a concise status update.
  5. Include the actual date range used in the final summary.

Guardrails

  • Be extremely concise and information-dense.
  • Prioritize substantial behavior or architecture changes.
  • Omit cosmetic-only changes (formatting, imports, minor renames).
  • Do not infer intent or motivation. Describe changes functionally.

Output

  • One short summary suitable for a status update
  • Real date range
  • Optional 2-5 bullets for major changes only
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday Changed · -1 lines 479813c9abaa
  2. 10d ago First seen · 33 lines · 24 tokens per session scan A 6070302aebca

Subscribe to this mod's changes

what-did-i-get-done is a skill published in the GitHub repository michael-denyer/pstack-claude (281 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 222 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

git-advanced-workflows

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

wshobson/agents · 54 tokens

workflow-patterns

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

wshobson/agents · 35 tokens

block-no-verify-hook

Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.

wshobson/agents · 46 tokens

research-git

Scans public GitHub repos for agent skills, dev practices, and code patterns. Use when enriching skills, setting team policy, or researching a build domain.

vasilyu1983/AI-Agents-public · 36 tokens

cross-repo-cache

Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…

closedloop-ai/claude-plugins · 81 tokens

dev-git-commit-message

Generates or validates Conventional Commits messages from staged diffs. Use when drafting commit messages, checking repo rules, or inferring scope from changed files.

vasilyu1983/AI-Agents-public · 38 tokens