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.
curl -O https://raw.githubusercontent.com/ThoBustos/openyoko/main/.claude/skills/weekly-calls/SKILL.mdgit 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-calls)<a href="https://agentmods.dev/skills/thobustos/openyoko/weekly-calls"><img src="https://agentmods.dev/badge/skills/thobustos/openyoko/weekly-calls.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.1 | $0.00000 | $0.02055 |
| Opus 5 | $0.00000 | $0.01027 |
| Sonnet 5 | $0.00000 | $0.00411 |
| Haiku 4.5 | $0.00000 | $0.00205 |
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 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.
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 in03_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
- Find the vault at
../my-vault/relative to personal-agent-os (typically/Users/username/Documents/projects/my-vault/) - Search
03_PROJECTS/for a folder matching the project name (case-insensitive) - If not found, list available projects and ask user to clarify
Step 2: Determine Week Range
- Parse the optional week argument:
- If
W03orw03format: interpret as current year's week 3 - If
2026-W03format: use exact ISO week - If no week specified: find the most recent week that has calls
- If
- Calculate the date range for that ISO week (Monday-Sunday)
Step 3: Gather Calls
- Read all files in the project's
Calls/folder - Filter to only calls within the target week's date range
- Parse dates from filenames (format:
YYYY-MM-DD-*.md) - 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
## Decisionssection or decision-related content - Insights: Key learnings from
## Key Pointssection - Action Items: Lines starting with
- [ ]or content under## Action Items - Notable Quotes: From
## Notable Quotessection (preserve the> "quote" - attributionformat) - Open Questions: Unresolved items, things marked TBD, or explicit questions
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 · 261 lines · 0 tokens per session scan A 04a037739c4e
weekly-calls is a skill published in the GitHub repository ThoBustos/openyoko (10 stars, last pushed 6d 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.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.