What is end-of-week-summary?

A weekly report generator that summarizes Slack activity, colleague contributions, outstanding action items, and thanks.

Use it to prepare a weekly digest covering your activity, a monitored Slack channel, team contributions, follow-up work, and recognition.

It removes the need to manually gather weekly updates from Slack and daily notes.

end-of-week-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-week-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-week-summary/github.svg)](https://agentmods.dev/skills/tomzx/agents/end-of-week-summary)

Your own site

<a href="https://agentmods.dev/skills/tomzx/agents/end-of-week-summary"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-of-week-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-week-summary"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-of-week-summary.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 1,299 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.00024	$0.01299
Opus 5.5	$0.00010	$0.00520
Sonnet 5.5	$0.00005	$0.00260
Haiku 4.5	$0.00002	$0.00130

Measured 22d ago against content hash ff1748dcf87c, 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-week-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-week-summary/SKILL.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 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 YEAR=!date +%Y WEEK=!date +%V WEEK_START=!date -d "$(date +%Y-%m-%d) -$(( $(date +%u) - 1 )) days" +%Y-%m-%d WEEK_START_MINUS_ONE=!date -d "$WEEK_START - 1 day" +%Y-%m-%d TOMORROW=!date -d "tomorrow" +%Y-%m-%d

Generate End-of-Week Summary

Produces a weekly digest covering personal Slack activity, a monitored Slack channel, each colleague's contributions, outstanding action items, and thanks from the week.

Prerequisites

SLACK_TOKEN, SLACK_COOKIE, and SLACK_USER in .env (same credentials used by collect_individual_threads.py)
NOTES_DIR environment variable set, containing daily .slack.md note files
COLLEAGUES environment variable set (resolved via ~/.agents/scripts/get-env COLLEAGUES)
SLACK_USER environment variable set (resolved via ~/.agents/scripts/get-env SLACK_USER; Slack username, e.g. tom.rochette)
HELP_ML_CHANNEL_ID environment variable set (resolved via ~/.agents/scripts/get-env HELP_ML_CHANNEL_ID; Slack channel id for #help-ml-infrastructure)
~/.agents/scripts/get-env utility available

Pipeline

Personal Slack  --> {BASE_DIR}/{YEAR}/weekly/{WEEK}/slack.md
#help-ml-infra  --> {BASE_DIR}/{YEAR}/weekly/{WEEK}/slack.help-ml-infrastructure.md
Colleagues      --> {BASE_DIR}/{YEAR}/weekly/{WEEK}/slack/{COLLEAGUE}.md (parallel)
                    {BASE_DIR}/{YEAR}/weekly/{WEEK}/slack.colleagues.md
Action Items    --> {BASE_DIR}/{YEAR}/weekly/{WEEK}/action-items.md
Thanks          --> {BASE_DIR}/{YEAR}/weekly/{WEEK}/thanks.md

Steps

1. Summarize Personal Slack Activity

Summarize .slack.md files in {BASE_DIR} from the week ending {TODAY}. Write to {BASE_DIR}/{YEAR}/weekly/{WEEK}/slack.md.

2. Summarize #help-ml-infrastructure Channel

Fetch messages from the #help-ml-infrastructure Slack channel during the week ending {TODAY} using build_thread_kb.py. WEEK_START is Monday of the current week; TOMORROW is used as the exclusive upper bound.

Read the full file on GitHub · 124 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 · -1 lines ff1748dcf87c
1mo ago First seen · 125 lines · 24 tokens per session scan A ea308bd21a7a

Subscribe to this mod's changes

end-of-week-summary is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 1,299 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.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens