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 skills add mxyhi/ok-skills --skill ledger-tasks-yylogit clone --depth 1 https://github.com/mxyhi/ok-skillsWrote 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/mxyhi/ok-skills/ledger-tasks-yylo)<a href="https://agentmods.dev/skills/mxyhi/ok-skills/ledger-tasks-yylo"><img src="https://agentmods.dev/badge/skills/mxyhi/ok-skills/ledger-tasks-yylo/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.
<a href="https://agentmods.dev/skills/mxyhi/ok-skills/ledger-tasks-yylo"><img src="https://agentmods.dev/badge/skills/mxyhi/ok-skills/ledger-tasks-yylo.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.00771 |
| Opus 5.5 | $0.00023 | $0.00308 |
| Sonnet 5.5 | $0.00011 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
ledger-tasks-yylo 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 yesterday.
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YYLO Ledger Task Management
Use this skill when a coding agent needs durable, reviewable task state that lives in the repository instead of a chat transcript. YYLO Ledger is the source of truth for task state; this skill teaches the working loop.
Adapted from the canonical ledger-tasks-yylo skill in yylo-dev/yylo-skills; see the upstream SKILL.md for the full CLI reference (archives, multi-directory merges, controller routing).
When to Use
- Decide which task is safe to start next (
ready= all blockers done) - Start assigned work and record an evidence receipt (
mark in_progress --response) - Close a task with what changed and how it was tested (
mark done --response --commit) - Declare dependencies between tasks before creating them
- Sequence parallel work topologically (
order --scores)
Workflow
- Pick work:
yy ledger ready(oryy ledger list --status todo,in_progress). - Inspect full state before any mutation:
yy ledger get TASK_ID(includes resolvedblocked_byand related tasks). - Start:
yy ledger mark in_progress --id TASK_ID --response "Starting: <plan>". - Finish:
yy ledger mark done --id TASK_ID --response "Done: <what> — tested <how>" --commit <sha>. - If the task cannot proceed, keep the blocker explicit instead of closing it silently.
Core Commands
yy ledger create "Short, one-iteration task" --status backlog --tags feature,backend
yy ledger list --status todo,in_progress --limit 10
yy ledger search --tag backend --open
yy ledger get TASK_ID
yy ledger update TASK_ID --tags backend,urgent
yy ledger deps add --id TASK_ID --blocked-by BLOCKER1 BLOCKER2
yy ledger ready --tag backend
yy ledger order --scores
yy ledger archive TASK_ID # soft delete, preserves data
Inline body markup is parsed on create/update, so dependencies can be declared in prose:
[blocked_by]TASK_ID[/blocked_by] — this task waits on TASK_ID
[task_id]RELATED_ID[/task_id] — cross-reference a related task
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 61 lines · 57 tokens per session scan A 056f0d221a90
ledger-tasks-yylo is a skill published in the GitHub repository mxyhi/ok-skills (500 stars, last pushed 2d ago), licensed Apache-2.0. It adds 57 tokens to every session and 771 once invoked, about $0.0002 per session on Opus 5.5. 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-10-19.
Other skills, from other repositories
outlook-calendar
A skill for managing Microsoft Outlook and Microsoft 365 calendar events through a connected account.
cron
Use this skill only for scheduled or recurring tasks. Manage jobs with qwenpaw cron list/create/get/state/pause/resume/delete/run, and always pass --agent-id explicitly.
cron
A scheduling tool for running tasks at a future time or repeating them on a set schedule. It manages scheduled jobs such as reminders, checks, and reports.
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
infrastructure-project
Skill for the project management infrastructure module providing multi-project discovery, structure validation, and metadata extraction. Use when discovering active projects, validating project directory structure, or extracting project configuration metadata.
to-tickets
Slice a spec or a ticket into tracer-bullet tickets with blocking edges, published through the repo's tracker: .specs/tickets/ .md by default.