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/dailynpx skills add ThoBustos/openyoko --skill dailygit 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/daily)<a href="https://agentmods.dev/skills/thobustos/openyoko/daily"><img src="https://agentmods.dev/badge/skills/thobustos/openyoko/daily.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.07897 |
| Opus 5 | $0.00000 | $0.03948 |
| Sonnet 5 | $0.00000 | $0.01579 |
| Haiku 4.5 | $0.00000 | $0.00790 |
Grade A, and why
daily 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 5d 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 — 867 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/daily Skill
Morning planning or evening reflection ritual. Run daily to stay aligned with your weekly intentions.
Usage
/daily [morning|evening|quick]
Examples:
/daily- Full daily reflection + planning/daily morning- Full flow, morning greeting/daily evening- Full flow, evening greeting/daily quick- Fast 3-min version: calendar → Top 3 → energy → done
Modes:
morning/evening- Changes greeting tone, full flowquick- Streamlined flow for low-energy days (skips grounding questions, open exploration, detailed backlog review)
Architecture: Skill vs Extension
This skill file (generic orchestrator):
- Flow steps and logic
- What sources to check (TODO.md, backlogs, journal, scans)
- How to display information (table formats, categories)
- Processing rules (priority indicators, deduplication)
- No personal data, account names, or vault-specific config
Extension file in vault (personal config):
- Which calendar IDs to check
- Which accounts to use
- Custom flow modifications (skip steps, add steps)
- Personal rules (e.g., "GYM days are Tue + Thu")
- Post-skill actions (git push, notifications)
Location: {{vault}}/00_SYSTEM/extensions/daily.md
This separation allows the skill to be shared/open-sourced while keeping personal config private in the vault.
Quick Mode Flow
When /daily quick is invoked, run this streamlined 3-minute flow:
Step 0 → Git commit/push (silent)
Step 0.1 → Check meeting inbox for context (silent)
Step 0.5 → Load extension (silent)
Step 0.75→ Check date (silent)
Step 1 → Read context (silent) - still scan ALL task sources
Step 2 → Gather (abbreviated):
0. Important dates (if any)
1. Calendar + auto-build Day Plan
2.5. Incomplete task rollover (show list, ask which to add)
3. Today planning (#1 focus, fill [TBD])
4. Energy level only (skip pillars)
7. Task count + urgent only (from ALL sources)
Step 3-6 → Categorize, confirm, write, verify (same)
Step 7-8 → Complete + extension (same)
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.
- 5d ago First seen · 867 lines · 0 tokens per session scan A b114907fb13c
daily 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 7,897 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.