A weekly planning process that selects three to five important outcomes and distributes them across the days of the week. An outcome is a finished result, not merely an activity.

Use it to turn deadlines and priorities into a focused weekly plan with clear, checkable results.

It prevents an overloaded to-do list from spreading attention across too many tasks and makes success easier to judge.

plan-woche — Skill for Claude Code and Codex by sebaskauf: A weekly planning process that selects three to five…

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.

agentmods

npx agentmods add skills/sebaskauf/agentic-os/plan-woche

Any agent

npx skills add sebaskauf/agentic-os --skill plan-woche

Clone the repo

git clone --depth 1 https://github.com/sebaskauf/agentic-os

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/sebaskauf/agentic-os/plan-woche.svg)](https://agentmods.dev/skills/sebaskauf/agentic-os/plan-woche)

Your own site

<a href="https://agentmods.dev/skills/sebaskauf/agentic-os/plan-woche"><img src="https://agentmods.dev/badge/skills/sebaskauf/agentic-os/plan-woche.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,660 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.00157	$0.01660
Opus 5	$0.00078	$0.00830
Sonnet 5	$0.00031	$0.00332
Haiku 4.5	$0.00016	$0.00166

Measured 5d ago against content hash 017600cd26c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

plan-woche 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 5d 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/plan-woche/SKILL.md · 101 lines

How it starts

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

Wochenplan - Fokus auf Wenigem statt Vielem

Dieser Skill hilft dem User, seine Woche zu planen. Das Ziel ist nicht eine endlose To-do-Liste, sondern Klarheit: Welche 3 bis 5 Outcomes machen diese Woche zu einem Erfolg? Alles andere ist nachrangig.

Der wichtigste Grundgedanke: Eine Woche hat begrenzte Zeit und Energie. Wer sich 15 Dinge vornimmt, erledigt am Ende oft das Falsche und fühlt sich trotzdem ausgelaugt. Wer sich auf wenige, klar definierte Outcomes konzentriert, kommt wirklich voran. Dein Job ist es, den User zu genau dieser Reduktion zu führen, nicht ihn mit Vollständigkeit zu erschlagen.

Ein Outcome ist ein Ergebnis, kein Tätigkeitswunsch. "An der Webseite arbeiten" ist kein Outcome. "Landingpage online und erreichbar" ist eines. Achte beim Formulieren immer darauf, dass man am Ende der Woche eindeutig mit Ja oder Nein sagen kann, ob es erreicht wurde.

Ablauf

Schritt 1 - Kontext sammeln (read-only)

Bevor du planst, verschaffe dir ein Bild. Frage den User nach den großen Themen der Woche, falls er sie nicht schon genannt hat. Zwei, drei gezielte Fragen reichen:

Was muss diese Woche unbedingt fertig werden? (harte Deadlines, Termine)
Was würde dich am Sonntagabend zufrieden zurückblicken lassen?
Gibt es feste Termine oder Blocker, um die herum geplant werden muss?

Wenn der User ein Notiz-System oder einen Vault nutzt (z.B. Obsidian, Notion-Export, ein Projektordner), darfst du dort lesend nach offenen Aufgaben, früheren Wochenplänen oder einem Backlog suchen. Nutze dafür Glob und Read. Greife nur auf Verzeichnisse zu, die der User dir nennt oder die offensichtlich dazugehören. Beispiele für Suchorte:

{{NOTIZEN_ORDNER}} - der Ordner mit den Notizen/Aufgaben des Users. Ersetze {{NOTIZEN_ORDNER}} durch deinen echten Pfad, oder lass den User ihn nennen.
letzter Wochenplan (Dateinamen wie wochenplan-*.md oder week-*.md), um zu sehen, was offen blieb.

Wenn du keinen Zugriff brauchst oder der User nichts nennt, plane einfach mit dem, was er dir im Chat gibt. Erfinde niemals Aufgaben dazu.

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

5d ago First seen · 101 lines · 157 tokens per session scan A 017600cd26c2

Subscribe to this mod's changes

plan-woche is a skill published in the GitHub repository sebaskauf/agentic-os (2 stars, last pushed 1mo ago), licensed MIT. It adds 157 tokens to every session and 1,660 once invoked, about $0.0008 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.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens