weekly-review

weekly-review is a skill for Claude Code from samkawsarani/sams-product-plugins. It costs 54 tokens per session (1,203 once invoked), scanned A, original, MIT.

A review tool that summarizes the past week's completed work, progress toward goals, blockers, stalled tasks, and priorities for the next week.

In plain words
What is it for?
Reviewing TASKS.md, identifying finished and unfinished work, checking goals, and planning the following week.
Why use it?
It gives you a regular record of what moved forward and what needs attention.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter.

Part of the weekly-review plugin — 1 skill shipped together

Good fit Reviewing TASKS.md, identifying finished and unfinished work, checking goals, and planning the following week.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/samkawsarani/sams-product-plugins/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.

Any agent
npx skills add samkawsarani/sams-product-plugins --skill weekly-review
Clone the repo
git clone --depth 1 https://github.com/samkawsarani/sams-product-plugins

Made for: Claude Code.

Or install weekly-review, the plugin that ships this one along with the rest of its 1 skill.

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/skills/samkawsarani/sams-product-plugins/weekly-review/github.svg)](https://agentmods.dev/skills/samkawsarani/sams-product-plugins/weekly-review)
Your own site
<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/weekly-review"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/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/skills/samkawsarani/sams-product-plugins/weekly-review"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/weekly-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,203 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.00054 $0.01203
Opus 5 $0.00027 $0.00602
Sonnet 5 $0.00011 $0.00241
Haiku 4.5 $0.00005 $0.00120

Measured 11d ago against content hash fb27645efe64, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d 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.

plugins/weekly-review/skills/weekly-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.

Context

Today's date: $TODAY

If user says "quick" → use Quick Version.


Step 0: Determine Date Range

Calculate the reporting period:

  • If today is Monday, the past week = previous Monday through yesterday (Sunday)
  • Otherwise, the past week = most recent Monday through most recent Sunday
  • Display the date range in all section headers

Step 1: Review Completed Work

  1. Read tasks/TASKS.md
  2. Find all checkboxes marked done: - [x]
    • Format varies — a task might be a heading with checkboxes under it, a standalone checkbox, or a mix
    • Use context to determine what "done" means for each item; don't rely on nesting structure
  3. Items still - [ ] = active or not yet started

Output format:

## This Week's Completed Work ([Date Range])

### Shipped
- [Item that went live or was delivered externally]

### Completed (internal)
- [Item that was finished internally]

### Still In Progress
- [Task] — [brief status from context]

**Highlights:**
- [Major win or milestone]
- [Concerning pattern or gap, if any]
  • If nothing is checked off in the Active section, say so and ask the user to call out what got done before proceeding
  • Distinguish Shipped (external delivery) from Completed (internal) based on task context

Step 2: Check Goal Progress

  1. Find and read GOALS.md
  2. For each goal, match completed and in-progress work from Step 1 to assess progress
  3. Flag goals with no activity this week

Output format:

## Quarterly Goal Progress

### Goal: [Goal Name]
**Status:** On Track | At Risk | Behind

**This week:**
- Shipped/completed: [items]
- In progress: [items]
- No activity: [yes/no]

**Velocity:** [Assessment — "Ahead of schedule", "Need to accelerate", etc.]

Step 3: Identify Blockers and Stalled Work

  1. Read tasks/TASKS.md Waiting On table
  2. Flag any items that have been waiting more than 7 days (compare "Since" date to today)
  3. Flag any In Progress items that seem stale (check if they've been in the list for a while without movement — ask user if unclear)

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.

  1. 11d ago First seen · 173 lines · 54 tokens per session scan A fb27645efe64

Subscribe to this mod's changes

weekly-review is a skill published in the GitHub repository samkawsarani/sams-product-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 1,203 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.