A weekly planning helper that reviews goals and unfinished work from the previous week and sets a focus for the current calendar week.

Use it for Monday kickoffs, choosing a few weekly outcomes, connecting daily work to broader goals, and deciding what to finish or drop.

It gives the week a clear direction and carries forward useful unfinished work instead of making planning start from nothing.

start-week — 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 start-week

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

Your own site

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

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

When invoked 584 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.00040	$0.00584
Opus 5	$0.00020	$0.00292
Sonnet 5	$0.00008	$0.00117
Haiku 4.5	$0.00004	$0.00058

Measured 7d ago against content hash 5578eaad6d57, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

start-week 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 7d 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/start-week/SKILL.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 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

Start Week

Sets intent for the ISO week: a small number of outcomes, how collaboration fits, and what to finish or drop from last week.

Prerequisites

NOTES_DIR set (via ~/.agents/scripts/get-env NOTES_DIR)
Optional: {BASE_DIR}/goals.md, {BASE_DIR}/team-goals.md
Optional: {BASE_DIR}/{YEAR}/weekly/{WEEK}/action-items.md (if end-of-week-summary already ran this week)
Optional: previous week's {BASE_DIR}/{YEAR}/weekly/<prev>/review.md or action-items.md for carryover

Steps

1. Resolve week context

Use ISO week {WEEK} and year {YEAR}. If today is early in the week, treat "last week" as the previous ISO week (handle year boundary by checking weekly folders under {BASE_DIR}/{YEAR}/weekly/).

2. Gather context

Read if they exist:

Prior week review.md or action-items.md under {BASE_DIR}/{YEAR}/weekly/
{BASE_DIR}/goals.md and {BASE_DIR}/team-goals.md
This week's action-items.md if it already exists

3. Synthesize (in chat unless the user asks for a file)

Deliver:

Theme (one line for the week)
Top 3 outcomes (measurable or clearly done or not done)
Carryover (explicitly scheduled or explicitly dropped)
Collaboration (who to sync with, what decisions are waiting)
Risks (capacity, dependencies, recurring meetings to trim)

4. Optional file output

If the user wants it persisted, write {BASE_DIR}/{YEAR}/weekly/{WEEK}/plan.md:

---
week: {WEEK}
year: {YEAR}
date: {TODAY}
---

# Week plan

## Theme
## Top 3 outcomes
## Carryover from last week
## Collaboration and decisions
## Risks and constraints

Relationship to other skills

end-of-week-summary and end-of-week-review populate reflection and action items; start-week should reference them when present.
Do not run the Slack or colleague pipelines from end-of-week-summary here unless the user explicitly asks for a weekly digest.

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

7d ago First seen · 70 lines · 40 tokens per session scan A 5578eaad6d57

Subscribe to this mod's changes

start-week is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 584 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

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

start-week