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-user-reviewgit 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-user-review)<a href="https://agentmods.dev/skills/yasdef/yasdef-core/yasdef-worker-user-review"><img src="https://agentmods.dev/badge/skills/yasdef/yasdef-core/yasdef-worker-user-review/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-user-review"><img src="https://agentmods.dev/badge/skills/yasdef/yasdef-core/yasdef-worker-user-review.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.00064 | $0.01258 |
| Opus 5 | $0.00032 | $0.00629 |
| Sonnet 5 | $0.00013 | $0.00252 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
yasdef-worker-user-review 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YASDEF Worker User Review
Use this skill for the ASDLC worker user review phase. This is an executing phase: edit runtime code, apply requested test/doc updates, and update .asdlc_worker/user_review.md when feedback yields a durable rule.
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.
User Review Rules
- User review writes runtime code and durable user-review rules.
- Treat step-plan
## Plan (ordered)as the phase-state source. Do not useimplementation_plan.mdtarget bullets as user-review proof state. - Record new blockers in
.asdlc_worker/blocker_log.md, unresolved questions in.asdlc_worker/open_questions.md, and durable technical decisions in.asdlc_worker/decisions.mdwhen the process rules require it. - Keep project-specific verification and review constraints in
AGENTS.md, not in this skill. - User review commits runtime and UR-rule changes on the
step-<step>-<feature-id>-user-reviewbranch.
Workflow
-
Build context:
uv run python .claude/skills/yasdef-worker-user-review/scripts/build_user_review_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 reviewing. It includes the phase contract, the review contract from the step plan, accepted decisions, the step-plan
## Applicable UR Shortlist, the design scope contract (## Goal,## In Scope,## Out of Scope), the current-step blocker/open-question sections, and pointers to the full.asdlc_worker/user_review.mdplus the local assets.The step plan is the review contract. The design artifact supplies only the scope boundary.
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 · 73 lines · 64 tokens per session scan A 966dbeee3910
yasdef-worker-user-review is a skill published in the GitHub repository yasdef/yasdef-core (5 stars, last pushed 24d ago), licensed MIT. It adds 64 tokens to every session and 1,258 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.