weekly-review

weekly-review is a command for Claude Code from KhaledSaeed18/dotclaude. It costs 97 tokens per session (972 once invoked), scanned A, original, MIT.

A weekly project review that gathers recent commits, pull requests, issues, decisions, research entries, and action items from a repository and workspace. It records what happened, what stalled, and a short plan for the next week.

In plain words
What is it for?
Use it to prepare a recurring engineering or research status review from repository evidence and workspace records.
Why use it?
It replaces scattered activity checks with one dated account of progress and unfinished work. Accumulated reviews make changes and overdue actions easier to trace over time.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Part of the productivity plugin — 8 skills, 3 commands shipped together

Good fit Use it to prepare a recurring engineering or research status review from repository evidence and workspace records.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/khaledsaeed18/dotclaude/weekly-review
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.

Clone the repo
git clone --depth 1 https://github.com/KhaledSaeed18/dotclaude

Made for: Claude Code.

Or install productivity, the plugin that ships this one along with the rest of its 8 skills, 3 commands.

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 weekly-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/weekly-review/github.svg)](https://agentmods.dev/commands/khaledsaeed18/dotclaude/weekly-review)
Your own site
<a href="https://agentmods.dev/commands/khaledsaeed18/dotclaude/weekly-review"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/weekly-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.

agentmods 80×15 button for weekly-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/khaledsaeed18/dotclaude/weekly-review"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/weekly-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 972 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.00097 $0.00972
Opus 5.5 $0.00039 $0.00389
Sonnet 5.5 $0.00019 $0.00194
Haiku 4.5 $0.00010 $0.00097

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

Security

Grade A, and why

weekly-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 24d 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.

.claude-plugin/plugins/productivity/commands/weekly-review.md · 73 lines

How it starts

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

Context

Options: $ARGUMENTS

Today: !date +%Y-%m-%d | Week start: !date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d

Commits this week (all branches):

!git log --all --since='7 days ago' --format=' %ad %h %s (%an)' --date=short 2>/dev/null | head -40

Pull requests touched this week:

!gh pr list --state all --search "updated:>=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)" --json number,title,state,mergedAt,author --jq '.[] | " #\(.number) [\(.state)] \(.title)"' 2>/dev/null | head -20

Issues closed this week:

!gh issue list --state closed --search "closed:>=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)" --json number,title --jq '.[] | " #\(.number) \(.title)"' 2>/dev/null | head -20

Decision log and research log entries this week:

!grep -h "^- $(date +%Y-%m)" DECISIONS.md docs/DECISIONS.md 2>/dev/null | tail -10; grep -c "^## $(date +%Y-%m)" RESEARCH_LOG.md 2>/dev/null | xargs -I{} echo "{} research log entries this month"

Previous review's plan:

!f=$(ls reviews/*.md docs/reviews/*.md 2>/dev/null | sort | tail -1); [ -n "$f" ] && awk '/^## Next week/{f=1;next} /^## /{f=0} f' "$f" | head -15 || echo "(no previous review)"

Task

Write reviews/<week-end-date>.md (or the existing reviews directory). Use --since to change the window and --author to filter commits to one person in a shared repo.

Structure

# Week ending 2026-09-21

## Done
- Shipped: PR #45 workflow-hooks (merged Tue). Evidence: link.
- ...
Grouped by theme, each with its evidence (commit, PR, issue, file). Nothing without evidence.

## Against last week's plan
| Planned | Outcome |
| Finish thesis chapter 2 outline | done (research/OUTLINE.md) |
| Run n=30 sweep | not started; blocked on GPU quota |

## Decisions
- From DECISIONS.md and meeting notes this week, one line each.

## Stalled or overdue
- Action items past due (from meeting notes, the research log's Open section, open PRs with no activity for 5+ days).

## Numbers
Commits, PRs merged, issues closed, notes written, words added to chapters (if a thesis is present, from git diff --shortstat on chapters/).

## Next week
- Three to five outcomes, each with a definition of done and, where useful, a day.

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

  1. 24d ago First seen · 73 lines · 97 tokens per session scan A 47d213a95403

Subscribe to this mod's changes

weekly-review is a command published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 972 once invoked, about $0.0004 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-22.