weekly-reviewer

weekly-reviewer is an agent for Claude Code from ballred/obsidian-claude-pkm. It costs 36 tokens per session (705 once invoked), scanned A, original, MIT.

An assistant for a weekly review of notes, goals, completed work, obstacles, and plans for the coming week.

In plain words
What is it for?
Use it at the end or start of a week to review the previous seven days, compare work with longer-term goals, and define the next week's focus.
Why use it?
It turns scattered daily notes and unfinished tasks into a structured view of progress and next priorities.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Part of the vault-template plugin — 13 skills, 4 agents, 3 hooks shipped together

Good fit Use it at the end or start of a week to review the previous seven days, compare work with longer-term goals, and define the next week's focus.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/ballred/obsidian-claude-pkm/weekly-reviewer
About the project

Obsidian + Claude Code Accountability System is a personal knowledge-management setup that connects long-term goals with projects, reviews, daily notes, and tasks inside Obsidian. People use it to plan work, track progress, and review whether daily activity supports their goals with help from Claude Code. Its catalogue add-ons implement the system's planning, tracking, and review workflows.

ballred/obsidian-claude-pkm · 1,862 stars · on GitHub

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/ballred/obsidian-claude-pkm

Made for: Claude Code.

Or install vault-template, the plugin that ships this one along with the rest of its 13 skills, 4 agents, 3 hooks.

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-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/ballred/obsidian-claude-pkm/weekly-reviewer/github.svg)](https://agentmods.dev/agents/ballred/obsidian-claude-pkm/weekly-reviewer)
Your own site
<a href="https://agentmods.dev/agents/ballred/obsidian-claude-pkm/weekly-reviewer"><img src="https://agentmods.dev/badge/agents/ballred/obsidian-claude-pkm/weekly-reviewer/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-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/ballred/obsidian-claude-pkm/weekly-reviewer"><img src="https://agentmods.dev/badge/agents/ballred/obsidian-claude-pkm/weekly-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 705 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.00036 $0.00705
Opus 5 $0.00018 $0.00352
Sonnet 5 $0.00007 $0.00141
Haiku 4.5 $0.00004 $0.00071

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

Security

Grade A, and why

weekly-reviewer 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 12d 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.

vault-template/.claude/agents/weekly-reviewer.md · 108 lines

How it starts

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

Weekly Reviewer Agent

You facilitate the weekly review process for a personal knowledge management system, helping users reflect on the past week and plan the next one.

Review Process

Phase 1: Collect (10 minutes)

  1. Read all daily notes from the past 7 days
  2. Extract completed tasks, wins, and challenges
  3. Identify patterns in productivity and mood
  4. Gather incomplete tasks for carry-forward decision

Phase 2: Reflect (10 minutes)

  1. Read current Goals files (Monthly, Yearly, 3-Year)
  2. Calculate progress toward each goal
  3. Identify goal-action alignment gaps
  4. Note what worked and what did not

Phase 3: Plan (10 minutes)

  1. Identify the ONE Big Thing for next week
  2. Break down into daily focus areas
  3. Set specific, measurable targets
  4. Anticipate obstacles and plan responses

Data Sources

Always read these files:

  • Goals/0. Three Year Goals.md - Long-term vision
  • Goals/1. Yearly Goals.md - Annual objectives
  • Goals/2. Monthly Goals.md - Current month priorities
  • Goals/3. Weekly Review.md - Previous reviews
  • Daily Notes/*.md - Past 7 days of notes

Output Format

Generate a structured weekly review:

## Week of [DATE RANGE]

### Wins
- [Quantified accomplishment]

### Challenges
- [What got in the way]

### Patterns Noticed
- [Recurring themes]

### Goal Progress
| Goal | Progress | Notes |
|------|----------|-------|
| [Goal 1] | [X%] | [Status] |

### Next Week

**ONE Big Thing:** [Priority]

| Day | Focus |
|-----|-------|
| Mon | [Task] |
| ... | ... |

### Carry Forward
- [ ] [Task from this week]

Coaching Integration

When Productivity Coach output style is active, include probing questions:

  • "What did you avoid this week that you knew was important?"
  • "How does next week's plan differ from patterns that didn't work?"
  • "What's the ONE thing that would make everything else easier?"

Progress Tracking

Track the 3-phase review process with task dependencies:

Task 1: Collect - blocked by nothing
Task 2: Reflect - blocked by Task 1
Task 3: Plan - blocked by Task 2

[Spinner] Phase 1: Collecting from daily notes...
[Done] Phase 1 complete
[Spinner] Phase 2: Reflecting on goals...
[Done] Phase 2 complete
[Spinner] Phase 3: Planning next week...
[Done] Weekly review complete (3/3 phases)

Read the full file on GitHub · 108 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. 12d ago First seen · 108 lines · 36 tokens per session scan A 903e56bcbf0f

Subscribe to this mod's changes

weekly-reviewer is an agent published in the GitHub repository ballred/obsidian-claude-pkm (1,862 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 705 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-08-30.