agentmods.dev

openyoko: Skill for Claude Code

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

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

A monthly reporting workflow that gathers a project's calls and combines them into a summary of the month's patterns and developing story.

In plain words
What is it for?
Use it to summarize the latest month with calls for a project, or choose a month such as 01 or 2026-01.
Why use it?
It saves you from reading each call separately and manually connecting repeated themes across the month.

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/monthly-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 monthly-calls

README.md
[![agentmods](https://agentmods.dev/badge/skills/thobustos/openyoko/monthly-calls/github.svg)](https://agentmods.dev/skills/thobustos/openyoko/monthly-calls)
Your own site
<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.

agentmods 80×15 button for monthly-calls

Your own site · 80×15
<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>
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,426 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.02426
Opus 5.5 $0.00000 $0.00970
Sonnet 5.5 $0.00000 $0.00485
Haiku 4.5 $0.00000 $0.00243

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

Security

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 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/monthly-calls/SKILL.md · 306 lines

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 in 03_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

  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 Month Range

  1. Parse the optional month argument:
    • If 01 or 1 format: interpret as current year's January
    • If 2026-01 format: use exact year-month
    • If no month specified: find the most recent month that has calls
  2. Calculate the date range for that month (1st to last day)

Step 3: Check for Weekly Summaries

  1. Look in Notes/ folder for existing weekly summary files matching pattern {{YYYY}}-W{{NN}}-calls.md
  2. Filter to weeks that fall within the target month
  3. If weekly summaries exist: use them as primary source (more efficient)
  4. 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

Read the full file on GitHub · 306 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 · 306 lines · 0 tokens per session scan A 7fc4ef0d7d23

Subscribe to this mod's changes

monthly-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,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.

Analytics and metricsProject management
Related

monthly-calls compared with skills from other repositories

monthly-calls next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
monthly-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