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-implementationgit 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-implementation)<a href="https://agentmods.dev/skills/yasdef/yasdef-core/yasdef-worker-implementation"><img src="https://agentmods.dev/badge/skills/yasdef/yasdef-core/yasdef-worker-implementation/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-implementation"><img src="https://agentmods.dev/badge/skills/yasdef/yasdef-core/yasdef-worker-implementation.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.00054 | $0.01320 |
| Opus 5 | $0.00027 | $0.00660 |
| Sonnet 5 | $0.00011 | $0.00264 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
yasdef-worker-implementation 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 8d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YASDEF Worker Implementation
Use this skill for the ASDLC worker implementation phase. This is the executing phase: edit runtime code and update the step plan checklist state.
Inputs
The yasdef prompt should provide:
- step id, for example
1.3 - feature id
- branch name
- step plan path
- design artifact path
- runtime implementation plan path
If any input is missing, inconsistent, or points to a missing required file, do not infer it from .asdlc_worker/feature_meta_sync.yaml or the runtime environment. Stop and ask the user for explicit instructions.
Phase Contract
- Artifact precedence: step plan is the primary execution source; design supplies scope boundary only.
- Scope boundary: use design
## Goal,## In Scope, and## Out of Scope; do not use design## Non-goals. - Execution state machine: step plan
## Plan (ordered)only. - Functional contract: implement step-plan translated FRs.
- Checklist updates: mark ordered bullets and FRs
[x]only when implemented and verified. - LAR rule: fetch in-scope locators before implementing dependent FRs; ask the user on fetch failure or ambiguity.
- Verification timing: targeted checks during implementation; full
AGENTS.mdgate once after all ordered bullets are[x]. - Completion protocol: run
check_implementation_readiness.pybefore the completion line. - Runtime plan gating: do not use
implementation_plan.mdtarget bullets as implementation-phase proof state.
Workflow
-
Run the context builder:
uv run python .claude/skills/yasdef-worker-implementation/scripts/build_implementation_context.py --step <step> --feature-id <feature-id> --step-plan <step-plan-file> --design <design-file> --runtime-plan <runtime-plan> -
Read the printed context before editing. It includes the phase contract, the anti-regression checklist, the execution list, step-plan execution context, and design scope contract.
The step plan is the primary execution source. The design artifact supplies only the scope boundary:
## Goal,## In Scope, and## Out of Scope.
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.
- 8d ago First seen · 94 lines · 54 tokens per session scan A 40a5c99f1606
yasdef-worker-implementation is a skill published in the GitHub repository yasdef/yasdef-core (5 stars, last pushed 21d ago), licensed MIT. It adds 54 tokens to every session and 1,320 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…