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/unloadnpx skills add ThoBustos/openyoko --skill unloadgit 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/unload)<a href="https://agentmods.dev/skills/thobustos/openyoko/unload"><img src="https://agentmods.dev/badge/skills/thobustos/openyoko/unload.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 | $0.00000 | $0.02568 |
| Opus 5 | $0.00000 | $0.01284 |
| Sonnet 5 | $0.00000 | $0.00514 |
| Haiku 4.5 | $0.00000 | $0.00257 |
Grade A, and why
unload 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/unload Skill
End-of-day brain dump with intelligent state synthesis. Clear your mind, see your week's reality, and prepare tomorrow.
Usage
/unload
When to use:
- End of day when brain is full
- Before bed to clear mental load
- When feeling overwhelmed with open loops
Key difference from /daily:
/daily= structured morning/evening Q&A ritual with calendar, pillar tracking/unload= pure mind-clearing dump + intelligent state synthesis + tomorrow prep
Prerequisites
Before running this skill, check:
-
Current week journal exists - Look for
{{vault}}/02_JOURNAL/Weekly/{{YYYY}}-W{{WW}}.md- IF MISSING: "You don't have a week journal yet. Would you like to run /weekly first to set up your week?"
-
GLOBAL_STATE.md exists - Check
{{vault}}/00_SYSTEM/GLOBAL_STATE.md- IF MISSING: "No vault found. Run /onboarding first."
Flow
Phase 1: Context Gathering (Silent)
Read these files without outputting anything:
System Core:
{{vault}}/00_SYSTEM/GLOBAL_STATE.md- Current focus, energy, active projects{{vault}}/00_SYSTEM/TODO.md- All tasks, check staleness{{vault}}/00_SYSTEM/IMPORTANT_DATES.md- Anything for tomorrow
Journal:
4. {{vault}}/02_JOURNAL/Weekly/{{YYYY}}-W{{WW}}.md - Current week journal
- Extract: Top 3s (Personal + Professional), Keystone, Pillar Commitments
- Extract: All daily entries so far (Week Progress section)
- Extract: Running Thread items
Projects:
5. All active project _STATE.md files from GLOBAL_STATE's active_projects list
- Note staleness (>7 days = stale)
Activity:
6. {{vault}}/00_SYSTEM/OPS/activity-logs/{{YYYY}}-W{{WW}}.md - What was logged today
Goals:
7. {{vault}}/01_GOALS/{{YYYY}}.md - Year goals for context
8. {{vault}}/02_JOURNAL/Monthly/{{YYYY}}-{{MM}}.md - Month plan (if exists)
Calculate:
- Days since each project _STATE last updated
- Task completion status for Top 3s
- Pillar commitment progress (how many days hit)
- Any waiting/blocked items older than 7 days
- Tomorrow's calendar events (via MCP if available)
- Tomorrow's important dates
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 · 346 lines · 0 tokens per session scan A 09e0da18d6d1
unload is a skill published in the GitHub repository ThoBustos/openyoko (10 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,568 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.