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/tasksnpx skills add ThoBustos/openyoko --skill tasksgit 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/tasks)<a href="https://agentmods.dev/skills/thobustos/openyoko/tasks"><img src="https://agentmods.dev/badge/skills/thobustos/openyoko/tasks.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.02674 |
| Opus 5 | $0.00000 | $0.01337 |
| Sonnet 5 | $0.00000 | $0.00535 |
| Haiku 4.5 | $0.00000 | $0.00267 |
Grade A, and why
tasks 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 3d 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 — 460 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tasks Skill
Full visibility into all tasks with smart recommendations, inconsistency detection, and life goal alignment.
Usage
/tasks # Full task overview
/tasks acme # Focus on one project
/tasks check # Just check for inconsistencies
What This Skill Reads
| File | Purpose |
|---|---|
00_SYSTEM/TODO.md |
Master task list |
00_SYSTEM/GLOBAL_STATE.md |
Current focus, energy, active projects |
00_SYSTEM/PILLARS.md |
Life pillars for alignment |
00_SYSTEM/LIFE_VISION.md |
Identity and goals |
00_SYSTEM/IMPORTANT_DATES.md |
Upcoming dates/deadlines |
03_PROJECTS/*/_BACKLOG.md |
All project backlogs |
03_PROJECTS/*/_STATE.md |
Project states and focus |
02_JOURNAL/Weekly/{{current}}.md |
Week's commitments and pillar tracking |
01_GOALS/{{YYYY}}.md |
Year goals |
01_GOALS/{{YYYY}}-Q{{Q}}.md |
Quarter goals |
Flow
Phase 1: Silent Context Load
Read all files without outputting. Calculate:
From TODO.md:
- Count tasks per project in "This Week"
- Count tasks in Backlog, Waiting On, Someday
- Note any tasks without project tags
From Project Backlogs:
- All
_BACKLOG.mdfiles from active projects - Compare "Current Sprint" items vs TODO.md "This Week"
- Flag orphans (in backlog but not in TODO)
From GLOBAL_STATE.md:
- Current focus and Top 3 priorities
- Energy level
- Active projects list
From IMPORTANT_DATES.md:
- Any dates in the next 7 days
- Any dates this month
From Weekly Journal:
- Pillar commitments for the week
- Daily progress tracking
From Goals:
- Year and quarter goals for alignment check
Phase 2: Build Task Overview
Output the task overview grouped by timeline and project:
## Task Overview
### This Week (W{{WW}}: {{Mon Date}} - {{Sun Date}})
**#acme** ({{N}} tasks)
- [ ] Task 1
- [ ] Task 2
...
**#phoenix** ({{N}} tasks)
- [ ] Task 1
...
**#content** ({{N}} tasks)
- [ ] Task 1
...
**No project** ({{N}} tasks)
- [ ] Task 1
...
### Backlog ({{N}} items)
- [ ] #project Task description
...
### Waiting On ({{N}} items)
- [ ] #project Task (waiting since MM-DD)
...
### Someday ({{N}} items)
- [ ] Task description
...
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.
- 3d ago First seen · 460 lines · 0 tokens per session scan A f97ebc7690a4
tasks is a skill published in the GitHub repository ThoBustos/openyoko (10 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,674 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
finn-spec
Interview the user about a raw idea until confident, then file a build-ready issue in Linear. Use when asked to run Finn-loop's spec interview, draft a queue-ready issue, or plan a feature. Interactive — requires the user present; never run unattended.