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/monthly-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/monthly-calls)<a href="https://agentmods.dev/skills/thobustos/openyoko/monthly-calls"><img src="https://agentmods.dev/badge/skills/thobustos/openyoko/monthly-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.
<a href="https://agentmods.dev/skills/thobustos/openyoko/monthly-calls"><img src="https://agentmods.dev/badge/skills/thobustos/openyoko/monthly-calls.svg" alt="Reviewed on agentmods" width="80" 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.02426 |
| Opus 5 | $0.00000 | $0.01213 |
| Sonnet 5 | $0.00000 | $0.00485 |
| Haiku 4.5 | $0.00000 | $0.00243 |
Grade A, and why
monthly-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 9d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/monthly-calls Skill
Generate a comprehensive monthly call summary for a project, aggregating patterns and building a narrative arc.
Usage
/monthly-calls <project> [month]
Examples:
/monthly-calls acme- Summarize current/latest month's calls for Acme/monthly-calls techcorp 01- Summarize January calls for TechCorp/monthly-calls acme 2026-03- Specific year-month format
Arguments
project(required): Project name (case-insensitive, matches folder in03_PROJECTS/)month(optional): Month number (01-12) or ISO format (2026-01). Defaults to current/latest month 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 Month Range
- Parse the optional month argument:
- If
01or1format: interpret as current year's January - If
2026-01format: use exact year-month - If no month specified: find the most recent month that has calls
- If
- Calculate the date range for that month (1st to last day)
Step 3: Check for Weekly Summaries
- Look in
Notes/folder for existing weekly summary files matching pattern{{YYYY}}-W{{NN}}-calls.md - Filter to weeks that fall within the target month
- If weekly summaries exist: use them as primary source (more efficient)
- If not: fall back to scanning raw call files
Step 4: Gather Source Material
If using weekly summaries:
- Read each weekly summary for the month
- Extract already-synthesized decisions, insights, themes, momentum
If using raw calls:
- Read all files in
Calls/folder for the target month - Parse dates from filenames (format:
YYYY-MM-DD-*.md) - Extract using the same logic as weekly-calls skill
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.
- 9d ago First seen · 306 lines · 0 tokens per session scan A 7fc4ef0d7d23
monthly-calls is a skill published in the GitHub repository ThoBustos/openyoko (10 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,426 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.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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.
remove
Remove a deployed framework or addon from the current workspace.