What is end-of-day-summary?

A daily reporting workflow that summarizes GitHub work, Slack activity, and overall accomplishments, then creates a standup draft for the next workday. A standup is a short update about progress, plans, and blockers.

Use it to produce daily activity files, record accomplishments and blockers, and prepare the next day's team update.

It replaces a manual daily status report assembled from several tools and helps preserve a clear timeline of work.

end-of-day-summary — Skill for Claude Code and Codex by tomzx/agents

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/tomzx/agents

agentmods

npx agentmods add skills/tomzx/agents/end-of-day-summary

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/end-of-day-summary/github.svg)](https://agentmods.dev/skills/tomzx/agents/end-of-day-summary)

Your own site

<a href="https://agentmods.dev/skills/tomzx/agents/end-of-day-summary"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-of-day-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tomzx/agents/end-of-day-summary"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-of-day-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,142 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.

Model	Per session	Once invoked
Fable 5.1	$0.00032	$0.01142
Opus 5.5	$0.00013	$0.00457
Sonnet 5.5	$0.00006	$0.00228
Haiku 4.5	$0.00003	$0.00114

Measured 22d ago against content hash 643a4cfeba23, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

end-of-day-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 22d ago.

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.

skills/end-of-day-summary/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

BASE_DIR=!~/.agents/scripts/get-env NOTES_DIR TODAY=!date +%Y-%m-%d YESTERDAY=!date -d "yesterday" +%Y-%m-%d TOMORROW=!date -d "tomorrow" +%Y-%m-%d YEAR=!date +%Y MONTH=!date +%m DAY=!date +%d NEXT_WORKDAY=!date -d "$([ $(date +%u) -ge 5 ] && echo "next Monday" || echo "tomorrow")" +%Y-%m-%d

Generate End-of-Day Summary

Produces structured summaries of GitHub and Slack activity for the current day, a report of accomplishments and blockers, a timeline, and a standup draft for the next workday.

Prerequisites

SLACK_TOKEN, SLACK_COOKIE, and SLACK_USER in .env (same credentials used by collect_individual_threads.py)
gh CLI authenticated
summarize-github-activity script at $HOME/repos/git/personal-automation/others/summarize-github-activity
NOTES_DIR environment variable set (resolved via ~/.agents/scripts/get-env NOTES_DIR)
SLACK_USER environment variable set (resolved via ~/.agents/scripts/get-env SLACK_USER; Slack username, e.g. tom.rochette)
~/.agents/scripts/get-env utility available

Pipeline

GitHub Activity --> {BASE_DIR}/{YEAR}/{MONTH}/{DAY}.github.md
Slack Activity  --> {BASE_DIR}/{YEAR}/{MONTH}/{DAY}.slack.md
Overall Summary --> {BASE_DIR}/{YEAR}/{MONTH}/{DAY}.overall.md
Timeline        --> {BASE_DIR}/{YEAR}/{MONTH}/{DAY}.timeline.md
Standup         --> {BASE_DIR}/{YEAR}/{MONTH}/{NEXT_WORKDAY}.standup.md

Steps

1. Summarize GitHub Activity

$HOME/repos/git/personal-automation/others/summarize-github-activity tomzx {TODAY} {TODAY} Shopify,shop

Write output to {BASE_DIR}/{YEAR}/{MONTH}/{DAY}.github.md.

2. Summarize Slack Activity

Collect Slack threads for {TODAY} using collect_individual_threads.py. Slack's after:/before: search operators are exclusive, so use the day before and the day after {TODAY} as bounds:

SLACK_USER=`~/.agents/scripts/get-env SLACK_USER`

uv run skills/slack-kb-individual/collect_individual_threads.py \
  --user $SLACK_USER \
  --after {YESTERDAY} --before {TOMORROW} \
  -o {BASE_DIR}/{YEAR}/{MONTH}/{DAY}.slack.jsonl

Read the full file on GitHub · 133 lines

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.

22d ago Changed · -5 lines 643a4cfeba23
24d ago Changed 4b333d816aaa
1mo ago First seen · 138 lines · 32 tokens per session scan A e67978a8df74

Subscribe to this mod's changes

end-of-day-summary is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,142 once invoked, about $0.0001 per session on Opus 5.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-09-03.

Productivity Project management

OpenSourceManagement

Triages open issues, pull requests and GitHub Discussions across the principal's own open-source repos (the list in Config.md) via the gh CLI, ranks what needs attention with suggested replies, posts edit-in-place marker comments, diffs new Ollama library models against a local model box, and takes a private repo…

danielmiessler/LifeOS · 212 tokens

gsd-ns-manage

Invoke this Pi skill with /skill:gsd-ns-manage.

open-gsd/gsd-core · 16 tokens

to-spec

A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.

vinvcn/mattpocock-skills-zh-CN · 29 tokens

feature-prioritisation

Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…

mohitagw15856/pm-claude-skills · 103 tokens

design-handoff-brief

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…

mohitagw15856/pm-claude-skills · 83 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens