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 uthumany/uthy-legacy-os --skill acceptance-criteriagit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/acceptance-criteria)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/acceptance-criteria"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/acceptance-criteria/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/uthumany/uthy-legacy-os/acceptance-criteria"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/acceptance-criteria.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.00036 | $0.01125 |
| Opus 5 | $0.00018 | $0.00562 |
| Sonnet 5 | $0.00007 | $0.00225 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
acceptance-criteria 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 12d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acceptance Criteria
Overview
Acceptance criteria define when a story is "done." They're the shared understanding between product, engineering, and QA of what must be true for the feature to be accepted. Well-written criteria prevent ambiguity and reduce rework. This skill teaches the Given/When/Then format from Behavior-Driven Development (BDD).
When to Use
- Writing or reviewing user stories
- Defining scope for a sprint or release
- Handing off requirements to QA
- Creating a Definition of Done for your team
- Don't use for: non-functional requirements (performance, security — separate criteria), exploratory work, or creative tasks
Instructions
1. Use Given/When/Then Format
Scenario: [Title describing the scenario]
Given [context / preconditions]
When [action / event]
Then [expected outcome]
Given sets up the context — what state must exist before the action. When describes the trigger — what the user does or what happens. Then describes the expected result — what should be observable.
2. Follow Best Practices
- One scenario per behavior — Don't test multiple things in one scenario
- Use concrete examples — "Given user has 3 active projects" not "Given user has projects"
- Be deterministic — Same inputs always produce same results
- Focus on outcomes, not implementation — THEN describes what happens, not how
- Include edge cases — Empty states, error states, permission boundaries
3. Use AND/OR for Combinations
Scenario: Admin approves a team member's invitation
Given the admin is logged in
And there is a pending invitation for [email protected]
When the admin clicks "Approve"
Then the invitation status changes to "Active"
And the user receives a welcome email
4. Write Rule-Oriented Criteria
For features with many variations, write rule-oriented criteria:
Rule: Team members can see projects based on their role
Scenario: Owner can see all projects
Given I am the team owner
When I open the dashboard
Then I see all projects in the team
Scenario: Member can only see assigned projects
Given I am a team member
And I am assigned to projects A and B
When I open the dashboard
Then I see projects A and B
And I do NOT see project C
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.
- 12d ago First seen · 135 lines · 36 tokens per session scan A 6a3f1fa557b1
acceptance-criteria is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 1,125 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-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…