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/janyork/llm-wiki-cli/using-todonpx skills add JanYork/llm-wiki-cli --skill using-todogit clone --depth 1 https://github.com/JanYork/llm-wiki-cliWrote 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/janyork/llm-wiki-cli/using-todo)<a href="https://agentmods.dev/skills/janyork/llm-wiki-cli/using-todo"><img src="https://agentmods.dev/badge/skills/janyork/llm-wiki-cli/using-todo.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.00029 | $0.00468 |
| Opus 5 | $0.00015 | $0.00234 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
using-todo 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 2d 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.
What it actually says
Using LWC Todo
First run lwc config show. Continue only when todo.setting is enabled. A Skill trigger is not consent to enable Todo: when disabled, do not run Todo commands; explain that the user can opt in with lwc config set --todo enabled. A lifecycle Hook with a resolved agent_context includes only Todos explicitly tracked by that Agent context. Treat any Todo progress reminder for another context as unrelated and ignore it.
Use Todo only for independent future or deferred work. It is not the current execution plan and must never be converted to or from a Plan automatically.
- Add:
lwc todo add TITLE --tag TAG --cue TEXT --target-at RFC3339 --request-id ID. - After adding or explicitly claiming a Todo, bind it with
lwc --scope project|global todo track TODO_ID --context CONTEXT_ID, using only the opaque ID from the current Hook'sLWC_READINESS.agent_context. One context may track multiple Todos; never infer or copy another Agent's context. - Add one direct child with
--parent TODO_ID. Parentage is organization only: it does not cascade completion, create dependencies, or turn children into Plan steps. - Discover:
lwc todo list --limit 20,lwc todo list --parent TODO_ID, orlwc todo search QUERY --limit 20. - Inspect before mutation:
lwc todo show TODO_ID; pass its revision with--if-revision. - Reschedule with
todo update ... --target-at RFC3339; remove the time with--clear-target-at. - Finish or cancel with a specific result/reason; use
reopenbefore changing a closed Todo. - Stop reminders with exact, idempotent
todo untrack TODO_ID --context CONTEXT_ID; this removes only that context/Todo pair. - Use project/global for exact reads and writes. Use
--scope allonly for list/search. - On a revision or request conflict, reload and reconcile; never overwrite blindly.
- Do not use
--changesetwith Todo commands.
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.
- 2d ago Changed · +2 lines 5019d429d9af
- 6d ago First seen · 21 lines · 29 tokens per session scan A ac2c704ae303
using-todo is a skill published in the GitHub repository JanYork/llm-wiki-cli (52 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 468 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
ccc
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the…