What is end-of-week-review?

A weekly review that reflects on goal progress, time and attention patterns, team health, and changes for the following week.

Use it to review weekly notes and goals, then assess whether your work was building lasting value or losing value over time.

It turns scattered daily notes and team updates into a structured look back at what happened and what should change.

end-of-week-review — Skill for Claude Code and Codex by tomzx

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 tomzx/agents --skill end-of-week-review

Clone the repo

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

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

Your own site

<a href="https://agentmods.dev/skills/tomzx/agents/end-of-week-review"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-of-week-review/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-review"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-of-week-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,601 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.00048	$0.01601
Opus 5	$0.00024	$0.00800
Sonnet 5	$0.00010	$0.00320
Haiku 4.5	$0.00005	$0.00160

Measured 9d ago against content hash a2f585f20080, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

end-of-week-review 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 9d 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-review/SKILL.md · 173 lines

How it starts

The opening of the file, as written. The whole thing — 173 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 NEXT_WEEK=!date -d "next Monday" +%V

End-of-Week Review

Guides a structured weekly reflection connecting your week's work to goals, surfacing patterns in how you spent your time and attention, checking on team health, and deciding what to change next week.

Prerequisites

NOTES_DIR environment variable set (resolved via ~/.agents/scripts/get-env NOTES_DIR)
~/.agents/scripts/get-env utility available
Optional: daily .review.md files from the week in {BASE_DIR}/{YEAR}/{MONTH}/
Optional: daily .overall.md files from the week in {BASE_DIR}/{YEAR}/{MONTH}/
Optional: {BASE_DIR}/goals.md with current personal goals
Optional: {BASE_DIR}/team-goals.md with current team goals
Optional: {BASE_DIR}/{YEAR}/weekly/{WEEK}/slack.colleagues.md from end-of-week-summary
The audit-attention skill available (invoked in step 3)

Steps

1. Gather Context

Read the following files if they exist:

All *.review.md files from this week in {BASE_DIR}/{YEAR}/{MONTH}/
All *.overall.md files from this week in {BASE_DIR}/{YEAR}/{MONTH}/
{BASE_DIR}/goals.md
{BASE_DIR}/team-goals.md
{BASE_DIR}/{YEAR}/weekly/{WEEK}/action-items.md
{BASE_DIR}/{YEAR}/weekly/{WEEK}/slack.colleagues.md

2. Synthesize Patterns

Before asking questions, analyze the gathered data to identify:

Time allocation: Estimate what percentage of the week went to (a) goal-driven deep work, (b) collaboration and team support, (c) reactive/unplanned work, (d) administrative overhead.

Goal progress: For each goal in goals.md and team-goals.md, assess: not started / some progress / significant progress / completed.

Reactivity trend: Using the daily reactivity scores (if available), is the week trending better or worse than the previous pattern?

Team signals: From colleague summaries and notes, flag any team members who seem blocked, overloaded, disengaged, or who did something notable worth recognizing.

Read the full file on GitHub · 173 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.

9d ago First seen · 173 lines · 48 tokens per session scan A a2f585f20080

Subscribe to this mod's changes

end-of-week-review is a skill published in the GitHub repository tomzx/agents (8 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,601 once invoked, about $0.0002 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-09-03.

Planning Productivity

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

agentmail

Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.

paperclipai/paperclip · 30 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

the-open-agent/openagent · 17 tokens