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 yasdef/yasdef-core --skill yasdef-worker-plangit clone --depth 1 https://github.com/yasdef/yasdef-coreWrote 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/yasdef/yasdef-core/yasdef-worker-plan)<a href="https://agentmods.dev/skills/yasdef/yasdef-core/yasdef-worker-plan"><img src="https://agentmods.dev/badge/skills/yasdef/yasdef-core/yasdef-worker-plan/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/yasdef/yasdef-core/yasdef-worker-plan"><img src="https://agentmods.dev/badge/skills/yasdef/yasdef-core/yasdef-worker-plan.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.00056 | $0.02829 |
| Opus 5 | $0.00028 | $0.01414 |
| Sonnet 5 | $0.00011 | $0.00566 |
| Haiku 4.5 | $0.00006 | $0.00283 |
Grade A, and why
yasdef-worker-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 11d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YASDEF Worker Plan
Use this skill for one ASDLC worker planning iteration. The phase is analysis-only: do not implement runtime code.
Inputs
The yasdef prompt should provide:
- step id, for example
1.3 - feature id
- branch name
- design artifact path
- step plan output path
- runtime implementation plan path
- open-questions ledger path
- blockers ledger path
If any input is missing, inconsistent, or points to a missing required file/path, do not infer it from .asdlc_worker/feature_meta_sync.yaml or the runtime environment. Stop and ask the user for explicit instructions.
Artifact Model
- The step plan file under
.asdlc_worker/step_plans/is the single planning artifact for the step. build_plan_context.pyinitializes that file fromassets/step_plan_TEMPLATE.mdwhen it is missing.- After initialization, the file stops being a template copy and becomes the real planning artifact that will hand off to implementation once it is fully filled and passes readiness validation.
- The per-step ledgers under
.asdlc_worker/step_open_questions/and.asdlc_worker/step_blockers/are loop-state artifacts for yasdef. Their contents determine whether the planning phase needs another iteration.
Workflow
-
Build context:
uv run python .claude/skills/yasdef-worker-plan/scripts/build_plan_context.py --step <step> --feature-id <feature-id> --design <design-file> --plan-out <step-plan-file> --runtime-plan <runtime-plan> --open-questions <open-questions-file> --blockers <blockers-file> -
Read the printed context before editing. It includes the current step section, extracted design sections, the current step plan, the per-step ledgers, the requirements EARS file path as a pointer, and the bundled golden example.
Treat
assets/step_plan_TEMPLATE.mdas the structural contract for a new step plan. The context builder initializes the artifact when it is missing; keep its headings and section intent unless the user explicitly changes the planning contract.
What ships with it
5 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.
- 11d ago First seen · 159 lines · 56 tokens per session scan A 1b7dee28e78a
yasdef-worker-plan is a skill published in the GitHub repository yasdef/yasdef-core (5 stars, last pushed 23d ago), licensed MIT. It adds 56 tokens to every session and 2,829 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…