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.
npx agentmods add skills/thobustos/openyoko/weeklynpx skills add ThoBustos/openyoko --skill weeklygit clone --depth 1 https://github.com/ThoBustos/openyokoWrote 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.
[](https://agentmods.dev/skills/thobustos/openyoko/weekly)<a href="https://agentmods.dev/skills/thobustos/openyoko/weekly"><img src="https://agentmods.dev/badge/skills/thobustos/openyoko/weekly.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.05143 |
| Opus 5 | $0.00000 | $0.02572 |
| Sonnet 5 | $0.00000 | $0.01029 |
| Haiku 4.5 | $0.00000 | $0.00514 |
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 4d 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.
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_updatedin00_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 │
└──────────────────────────────────────────────────────────────────────┘
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.
- 4d ago First seen · 732 lines · 0 tokens per session scan A 43532c2c3a0a
weekly is a skill published in the GitHub repository ThoBustos/openyoko (10 stars, last pushed 3d 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…