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-plannpx skills add JanYork/llm-wiki-cli --skill using-plangit 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-plan)<a href="https://agentmods.dev/skills/janyork/llm-wiki-cli/using-plan"><img src="https://agentmods.dev/badge/skills/janyork/llm-wiki-cli/using-plan.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.00032 | $0.00460 |
| Opus 5 | $0.00016 | $0.00230 |
| Sonnet 5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
using-plan 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 today.
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 Plan
First run lwc config show. Continue only when plan.setting is enabled. A Skill trigger is not consent to enable Plan: when disabled, do not run Plan commands; explain that the user can opt in with lwc config set --plan enabled. A lifecycle Hook with a resolved agent_context includes only Plans explicitly tracked by that Agent context. Treat any Plan progress reminder for another context as unrelated and ignore it.
Use Plan only for the current coarse execution plan. It is independent from Todo and must never be converted to or from a Todo automatically.
- Create one objective, explicit done criteria, constraints, and ordered coarse steps.
- After creating or explicitly claiming a Plan, bind it with
lwc --scope project|global plan track PLAN_ID --context CONTEXT_ID, using only the opaque ID from the current Hook'sLWC_READINESS.agent_context. Never infer or copy another Agent's context. - Resume with
lwc plan brief PLAN_ID; it is bounded and contains no hidden reasoning. - Treat Hook
plan.trackingandplan.additional_trackingsas continuity cues for this context only. Follow the current step and planned next step, but callbriefbefore any mutation. - Use exact, idempotent
plan untrack PLAN_ID --context CONTEXT_IDbefore deliberately switching a context to another Plan; a conflictingtracknever replaces the current association. - Before mutation, inspect the current revision and pass
--if-revision. advancecompletes the focal step with a result and explicitly selects the next pending step.blockrecords a concrete blocker.reviserequires a reason and replaces only unfinished work.- Complete only after all steps are terminal, evidence is supplied, and done criteria were checked.
- Use project/global for exact reads and writes. Use
--scope allonly for current/list/search. - On a revision or request conflict, reload and reconcile; never overwrite blindly.
- Do not use
--changesetwith Plan 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.
- today Changed · +2 lines 104e41855899
- 4d ago First seen · 22 lines · 32 tokens per session scan A 536e9d763645
using-plan is a skill published in the GitHub repository JanYork/llm-wiki-cli (50 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 460 once invoked, about $0.0002 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
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
extract
Run the full Semantica semantic extraction pipeline on a file or selected text — NER, relations, events, coreference resolution, triplets, and validation. Clears result cache before each run. Returns Markdown tables with entity/relation/event/triplet results and inline validator warnings.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
kayba-stage-7-fixer
Implement the approved fixes from the action plan and log all changes. Trigger when the user says "run stage 7", "implement fixes", "apply action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md to exist.