SkillHub is a self-hosted registry where organizations publish, discover, version, and manage reusable skills for AI agents. Teams use it to share governed skill packages privately, with namespaces, role-based access control, audit logs, and CLI installation; the catalogue entries are skills and related agent integrations that can be managed through it.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/iflytek/skillhubnpx agentmods add skills/iflytek/skillhub/ledger-tasks-yyloWrote 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/iflytek/skillhub/ledger-tasks-yylo)<a href="https://agentmods.dev/skills/iflytek/skillhub/ledger-tasks-yylo"><img src="https://agentmods.dev/badge/skills/iflytek/skillhub/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/iflytek/skillhub/ledger-tasks-yylo"><img src="https://agentmods.dev/badge/skills/iflytek/skillhub/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.02347 |
| Opus 5.5 | $0.00023 | $0.00939 |
| Sonnet 5.5 | $0.00011 | $0.00469 |
| Haiku 4.5 | $0.00006 | $0.00235 |
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 23d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- kanban-workflow — 86% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YYLO Ledger CLI Reference
Use yy ledger for all commands. Before any operation, run yy ledger --version and yy ledger --help; the installed runtime's help is authoritative. Read the current task/board state before mutation, preserve the returned mutation receipt when offered, and never edit Markdown/store files directly to bypass controller routing or lifecycle state. If the required command group is absent, stop and request a Ledger upgrade rather than guessing or invoking mutable source code. Ledger 0.3.x exposes both the compatible flat task commands and the native ID-first record|task|wiki|workflow|artifact groups. yy kanban is a labelled compatibility alias for the same controller-routed task runtime.
Supported task contract
- Preflight installed
yy ledger --versionandyy ledger --help; command help is authoritative for the selected runtime. - Use the flat task surface for lifecycle task management. Use the dedicated native skills for wiki, workflow, and artifact Records rather than guessing their arguments.
- New operational PDRs, contracts, plans, reports, receipts, and evidence belong in typed Artifact Records, not product documentation, task bodies/responses, or new
.juno_task/specsfiles. - If a required native group is absent, fail closed and request a Ledger upgrade. Never invoke mutable source directly or write Ledger store files by hand.
- Read current task state before mutation, preserve mutation receipts where offered, and never bypass controller routing or lifecycle state with direct file edits.
- Normal discovery is hot-only unless an explicit cold-archive command is used.
Opt-in cross-project routing
Cross-project access is disabled by default. The source .juno_task/config.json must set kanbanRegistry.enabled: true and explicitly list allowedProjects; environment overrides are YYLO_LEDGER_REGISTRY_ENABLED and YYLO_LEDGER_REGISTRY_ALLOWED_PROJECTS. Register with yy ledger project add ALIAS --path /absolute/project, then route any command with --project ALIAS. The destination wrapper/runtime remains authoritative, and routing failures never fall back to the source board.
What ships with it
2 files 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.
- 23d ago First seen · 187 lines · 57 tokens per session scan A e1f8c4492c6e
ledger-tasks-yylo is a skill published in the GitHub repository iflytek/skillhub (5,223 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 2,347 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-09-23.
Other skills, from other repositories
pm-brainstorm
A guided brainstorming workflow for exploring a new product idea before detailed research or requirements work. It collects basic information about the product, users, and problem through staged questions.
pm-priority
A Chinese-language procedure for ranking several product requests when time or resources are limited. It supports scoring or grouping methods such as RICE, KANO, and MoSCoW to decide what should be done first.
start-super-pm
Use when starting any product management task - automatically detects task type and invokes appropriate PM skill using intelligent routing.
pm-change
A requirements-change workflow for recording a proposed change, assessing its effects, and deciding whether to approve it.
pm-user-story
A workflow for turning product requirements into user stories: short statements of what a user wants and why, with acceptance criteria for checking the result.
pm-agile
A workflow for setting up an agile development process, where work is delivered in repeated short cycles and reviewed regularly.