agentmods.dev

openyoko: Skill for Claude Code

.claude/skills/weekly-calls/SKILL.md

weekly-calls is a skill for Claude Code from ThoBustos/openyoko. It costs 0 tokens per session (2,055 once invoked), scanned A, original, MIT.

A weekly reporting workflow that gathers a project's calls and turns them into a summary for a selected week.

In plain words
What is it for?
Use it to summarize the latest week with calls for a project, or choose a specific week such as W03 or 2026-W03.
Why use it?
It saves you from reviewing separate call notes and assembling the week's report by hand.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is ThoBustos/openyoko's own configuration. It tells Claude Code how to work on openyoko itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything openyoko configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/username/Documents/projects/my-vault/.

not rated 9repo 2mo ago A scan 0 tokens original MIT
View source ↗ ThoBustos/openyoko
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-calls/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.

agentmods badge for weekly-calls

README.md
[![agentmods](https://agentmods.dev/badge/skills/thobustos/openyoko/weekly-calls/github.svg)](https://agentmods.dev/skills/thobustos/openyoko/weekly-calls)
Your own site
<a href="https://agentmods.dev/skills/thobustos/openyoko/weekly-calls"><img src="https://agentmods.dev/badge/skills/thobustos/openyoko/weekly-calls/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-calls

Your own site · 80×15
<a href="https://agentmods.dev/skills/thobustos/openyoko/weekly-calls"><img src="https://agentmods.dev/badge/skills/thobustos/openyoko/weekly-calls.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 2,055 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.00000 $0.02055
Opus 5.5 $0.00000 $0.00822
Sonnet 5.5 $0.00000 $0.00411
Haiku 4.5 $0.00000 $0.00205

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

Security

Grade A, and why

weekly-calls 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-calls/SKILL.md · 261 lines

How it starts

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

/weekly-calls Skill

Generate a comprehensive weekly call summary for a project.

Usage

/weekly-calls <project> [week]

Examples:

  • /weekly-calls acme - Summarize latest week's calls for Acme
  • /weekly-calls techcorp W03 - Summarize Week 3 calls for TechCorp
  • /weekly-calls acme 2026-W02 - Specific week format

Arguments

  • project (required): Project name (case-insensitive, matches folder in 03_PROJECTS/)
  • week (optional): Week number (W01-W53) or ISO week (2026-W03). Defaults to current/latest week with calls.

Instructions

When this skill is invoked, follow these steps:

Step 1: Locate Project

  1. Find the vault at ../my-vault/ relative to personal-agent-os (typically /Users/username/Documents/projects/my-vault/)
  2. Search 03_PROJECTS/ for a folder matching the project name (case-insensitive)
  3. If not found, list available projects and ask user to clarify

Step 2: Determine Week Range

  1. Parse the optional week argument:
    • If W03 or w03 format: interpret as current year's week 3
    • If 2026-W03 format: use exact ISO week
    • If no week specified: find the most recent week that has calls
  2. Calculate the date range for that ISO week (Monday-Sunday)

Step 3: Gather Calls

  1. Read all files in the project's Calls/ folder
  2. Filter to only calls within the target week's date range
  3. Parse dates from filenames (format: YYYY-MM-DD-*.md)
  4. Sort chronologically

Step 4: Extract from Each Call

For each call note, extract:

Header Info:

  • Date (from filename or header)
  • Attendees (from **Attendees:** field)
  • Context/Topic (from header or **Context:** field)

Key Content:

  • Decisions: Look for ## Decisions section or decision-related content
  • Insights: Key learnings from ## Key Points section
  • Action Items: Lines starting with - [ ] or content under ## Action Items
  • Notable Quotes: From ## Notable Quotes section (preserve the > "quote" - attribution format)
  • Open Questions: Unresolved items, things marked TBD, or explicit questions

Read the full file on GitHub · 261 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. 2mo ago First seen · 261 lines · 0 tokens per session scan A 04a037739c4e

Subscribe to this mod's changes

weekly-calls 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 2,055 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.

Project managementWriting and docs
Related

weekly-calls compared with skills from other repositories

weekly-calls next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
weekly-callsThoBustos/openyokoSkill92mo agoMITA0Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code