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/monthlynpx skills add ThoBustos/openyoko --skill monthlygit 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)<a href="https://agentmods.dev/skills/thobustos/openyoko/monthly"><img src="https://agentmods.dev/badge/skills/thobustos/openyoko/monthly.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.01924 |
| Opus 5 | $0.00000 | $0.00962 |
| Sonnet 5 | $0.00000 | $0.00385 |
| Haiku 4.5 | $0.00000 | $0.00192 |
Grade A, and why
monthly 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 6d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/monthly Skill
Monthly reflection and planning ritual. Run at the start of each month to score your pillars, reflect deeply, and set intentions for the coming month.
Usage
/monthly [month]
Examples:
/monthly- Current month reflection/monthly 01- January reflection/monthly 2026-02- Specific month
Prerequisites
Before running this skill, check:
-
Year goals exist - Look for
01_GOALS/{{YYYY}}.md- IF MISSING: "You don't have year goals set. Would you like to do a quick yearly planning session first?"
-
LIFE_VISION.md exists - Check
00_SYSTEM/LIFE_VISION.md- IF MISSING: "You haven't defined your life vision yet. Would you like to run /onboarding?"
-
GLOBAL_STATE.md is fresh
- IF STALE: Update before proceeding
Flow Overview
- Review the month (what happened)
- Score each pillar 1-10
- Answer reflection questions
- Review project portfolio
- Set month intentions
- Create month journal
- Update GLOBAL_STATE.md
- Offer to cascade into /weekly
Step 1: Gather Context
Read these files:
00_SYSTEM/GLOBAL_STATE.md- Current state00_SYSTEM/LIFE_VISION.md- Vision and identity word00_SYSTEM/PILLARS.md- Pillar definitions01_GOALS/{{YYYY}}.md- Year goals02_JOURNAL/Weekly/- All weeks from the past month03_PROJECTS/*/_STATE.md- All active project states
Summarize what you learn about the past month.
Step 2: Review the Month
Share with user:
- Summary of weeks from the past month
- Projects that were active
- Major events or shifts you noticed
Ask:
- "What were the highlights of this month?"
- "What were the lowlights or disappointments?"
- "What surprised you?"
Step 3: Score Each Pillar (1-10)
Go through each pillar and ask for a score:
"Let's score how you did on each pillar this month. 1 = neglected, 10 = thriving."
Body & Energy
Monthly lens: "What does your body need right now?"
- How did you treat your body this month?
- Score (1-10):
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.
- 6d ago First seen · 288 lines · 0 tokens per session scan A 9e3121475bed
monthly is a skill published in the GitHub repository ThoBustos/openyoko (10 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,924 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.