Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/mostafa-drz/claude-skills/workday-summary)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/workday-summary"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/workday-summary/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.
<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/workday-summary"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/workday-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00070 | $0.02941 |
| Opus 5 | $0.00035 | $0.01470 |
| Sonnet 5 | $0.00014 | $0.00588 |
| Haiku 4.5 | $0.00007 | $0.00294 |
Grade A, and why
workday-summary 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workday Summary
Summarize everything you worked on into clean, grouped bullet points — ready for timesheets, standups, or end-of-day logs.
Preferences
Read ~/.claude/skills/workday-summary/preferences.md using the Read tool. If not found, no preferences are set.
Context
On startup, use Bash to gather: current date, git user email (git config user.email), GitHub username (gh api user -q .login), and any git repos under the working directory. Skip any that fail.
Command routing
Check $ARGUMENTS:
help→ display help then stopconfig→ interactive setup then stopreset→ delete~/.claude/skills/workday-summary/preferences.md, confirm, stop- anything else (including empty) → run the summary
Flags
Parse from $ARGUMENTS (use $0, $1 shorthand for positional args):
--today(default) — summarize today's work--yesterday— summarize yesterday's work--week— summarize this week's work--since "date"— summarize since a specific date/time--format <fmt>— output format:bullets(default),table,full-markdown,plain--group-by <mode>— grouping:ticket(default),project,chronological,none--no-time-estimates— omit time estimates from output--sources <list>— comma-separated:conversation,git,linear,github(default: all)--concise— summary only, no evidence--detailed— show evidence for each item
Help
Workday Summary — Summarize today's work for timesheets and standups
Usage:
/workday-summary Summarize today's session
/workday-summary --yesterday Yesterday's work
/workday-summary --week This week's work
/workday-summary --since "2026-02-28" Since a specific date
/workday-summary --format table Output as timesheet table
/workday-summary config Set preferences
/workday-summary reset Clear preferences
/workday-summary help This help
Options:
--today Default. Summarize today.
--yesterday Summarize yesterday.
--week Summarize this week (Mon-now).
--since "date" Since a specific date or time.
--format <fmt> bullets | table | full-markdown | plain
--group-by <mode> ticket | project | chronological | none
--no-time-estimates Omit time estimates
--sources <list> conversation,git,linear,github
--concise Summary only
--detailed Show evidence for each item
Examples:
/workday-summary End-of-day summary
/workday-summary --format table Timesheet-ready table
/workday-summary --week --concise Quick weekly recap
/workday-summary --sources git,linear Only git + Linear data
Current preferences:
(read from preferences.md)
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.
- today Changed · +2 lines · +70 tokens per session a29fe46194e2
- 12d ago First seen · 328 lines · 0 tokens per session scan A 8973c5f4d627
workday-summary is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 2,941 once invoked, about $0.0003 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-31.
Other skills, from other repositories
hydra
Fan multiple independent tasks out to SEPARATE Terminal.app windows, each running its own live claude session with exactly the context it needs — real parallel sessions with isolated context windows, not subagents. Confirms grouping/model/risk with the user before launching, delivers context invisibly, auto-tiles…
shipkit-work-memory
Log session progress and save resume state. Infers from conversation and git. Triggers: 'log progress', 'session summary', 'checkpoint', 'save progress', 'end session'.
session-update
Use when the user says "update session", "log progress", "checkpoint session", or invokes /session-update — especially before /clear or handoff.
interview-kit-builder
Generate a complete structured interview kit for a role — 3-5 role-specific competencies, one behavioral (STAR-format) question per competency, 1-5 scoring rubric with explicit behavioral anchors at each level, per-panel scorecards, interviewer debrief template.
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
claudeshrink
Automatically compress large natural text or log files before processing. Trigger when the user pastes massive text blobs, or asks to analyze a large file (logs, docs, transcripts), or provides a prompt that is too large for the context window. DO NOT trigger on source code files or structural data (JSON, XML).