A weekly planning routine that reviews the previous week, finds patterns, and prepares the next week around active projects.

Use it on Saturday, Sunday, or Monday to review projects, choose the week’s main tasks, update planning records, and carry relevant information forward. It expects a monthly plan, current state file, and at least one active project.

It reduces planning gaps by checking journals, goals, tasks, and project status before setting priorities.

How ThoBustos/openyoko configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ThoBustos/openyoko. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ThoBustos/openyoko/main/.claude/skills/weekly/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ThoBustos/openyoko

Made for: Claude Code.

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/thobustos/openyoko/weekly/github.svg)](https://agentmods.dev/skills/thobustos/openyoko/weekly)

Your own site

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

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

When invoked 5,143 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00000	$0.05143
Opus 5.5	$0.00000	$0.02057
Sonnet 5.5	$0.00000	$0.01029
Haiku 4.5	$0.00000	$0.00514

Measured 2mo ago against content hash 43532c2c3a0a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

weekly 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 2mo 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/skills/weekly/SKILL.md · 732 lines

How it starts

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

/weekly Skill

Weekly planning ritual that closes the previous week with pattern insights and sets up the new week with clarity. Run Saturday, Sunday, or Monday—flexible by design.

Usage

/weekly

Execution Window: Saturday evening → Monday morning (flexible)

Philosophy

Don't ask what you know. Read the data, surface the patterns, confirm accuracy.

Project-first thinking. Top 3s emerge from project review, not the other way around.

Think bigger. This isn't just task management—it's life alignment.

Zero entropy. Every mentioned entity gets updated. Nothing leaks.

Prerequisites

Before running this skill, check:

Current month plan exists - Look for 02_JOURNAL/Monthly/{{YYYY}}-{{MM}}.md
- IF MISSING: "You don't have a monthly plan yet. Would you like to run /monthly first to set your month intentions?"
GLOBAL_STATE.md is fresh - Check last_updated in 00_SYSTEM/GLOBAL_STATE.md
- IF STALE (>1 week): Note it, but proceed (will update at end)
At least one active project - Check GLOBAL_STATE for active_projects
- IF EMPTY: "You don't have any active projects listed. What are you working on?"

Flow Overview

┌──────────────────────────────────────────────────────────────────────┐
│  1. SILENT READ         │ Load all context without output            │
│  2. WEEK PORTRAIT       │ Pattern-oriented closing of last week      │
│  3. TASK TRIAGE         │ Scan unchecked tasks → roll over/drop      │
│  4. PROJECT-BY-PROJECT  │ Review each project: last week → this week │
│  5. TOP 3s              │ Synthesize from project review             │
│  6. PILLAR COMMITMENTS  │ Focus on gaps, confirm what's working      │
│  7. THINK BIGGER        │ Life-shaper questions for alignment        │
│  8. FULL RECAP          │ Show everything, confirm before writing    │
│  9. ATOMIC WRITE        │ Update all files in one pass               │
│ 10. VERIFY              │ Confirm all writes succeeded               │
│ 11. CASCADE OFFER       │ Offer to continue into /daily               │
└──────────────────────────────────────────────────────────────────────┘

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

2mo ago First seen · 732 lines · 0 tokens per session scan A 43532c2c3a0a

Subscribe to this mod's changes

weekly is a skill published in the GitHub repository ThoBustos/openyoko (9 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,143 tokens. 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.

Planning

weekly next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
weeklyThoBustos/openyoko	Skill	9	2mo ago	MIT	A	0	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

openyoko: Skill for Claude Code