acceptance-criteria

acceptance-criteria is a skill for Claude Code, Codex from pantheon-org/tekhne. It costs 49 tokens per session (1,194 once invoked), scanned A, original, MIT.

A skill for writing acceptance criteria: specific conditions that a feature or user story must meet to be considered complete. It can use Given/When/Then scenarios, a format that describes a starting situation, an action, and the expected result.

In plain words
What is it for?
It helps define done conditions, document normal and failure cases, and prepare requirements for development and testing.
Why use it?
It removes ambiguity between product, engineering, and quality-assurance teams by making requirements measurable and testable.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps define done conditions, document normal and failure cases, and prepare requirements for development and testing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pantheon-org/tekhne/acceptance-criteria
Install

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.

Any agent
npx skills add pantheon-org/tekhne --skill acceptance-criteria
Clone the repo
git clone --depth 1 https://github.com/pantheon-org/tekhne

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for acceptance-criteria

README.md
[![agentmods](https://agentmods.dev/badge/skills/pantheon-org/tekhne/acceptance-criteria/github.svg)](https://agentmods.dev/skills/pantheon-org/tekhne/acceptance-criteria)
Your own site
<a href="https://agentmods.dev/skills/pantheon-org/tekhne/acceptance-criteria"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/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.

agentmods 80×15 button for acceptance-criteria

Your own site · 80×15
<a href="https://agentmods.dev/skills/pantheon-org/tekhne/acceptance-criteria"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/acceptance-criteria.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,194 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01194
Opus 5 $0.00024 $0.00597
Sonnet 5 $0.00010 $0.00239
Haiku 4.5 $0.00005 $0.00119

Measured 7d ago against content hash 9b00c99883e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 7d 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.

skills/project-mgmt/issue-tracker-toolkit/acceptance-criteria/SKILL.md · 163 lines

How it starts

The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Acceptance Criteria

Navigation hub for writing measurable, test-ready acceptance criteria.

Use When

  • "Write acceptance criteria for this feature."
  • "Define done conditions for this story."
  • "Create testable requirements before implementation."
  • "Apply INVEST quality checks to this story."

When Not to Use

  • Architecture decisions and system design tradeoffs.
  • Deep technical specifications about implementation internals.

Workflow

  1. Capture user outcome and business intent.
  2. Select criteria format (Given/When/Then or rule-oriented).
  3. Draft must-pass criteria with measurable outcomes.
  4. Add negative and boundary scenarios.
  5. Validate with checklist before sign-off.

Worked Example

Starting Point (Vague Requirement):

"Users should be able to reset their password easily."

Step 1: Capture Intent

  • User outcome: User regains account access after forgetting password.
  • Business intent: Reduce support tickets; maintain security.

Step 2: Select Format Choose Given/When/Then (Gherkin) for clarity.

Step 3: Draft Must-Pass Criteria

Given a user is on the login page
When they click "Forgot Password"
Then a password reset form appears within 1 second

Given a user enters a valid email in the reset form
When they click "Send Reset Link"
Then an email is sent within 30 seconds
And the email contains a clickable reset link valid for 24 hours

Given a user clicks the reset link from the email
When they enter a new password (min 8 chars, 1 uppercase, 1 number)
And click "Update Password"
Then the password is updated
And they are redirected to login within 2 seconds

Step 4: Add Negative & Boundary Scenarios

Given a user enters an unregistered email
When they click "Send Reset Link"
Then they see "Email not found" message (no account enumeration)

Given a user's reset link has expired (>24 hours old)
When they click the link
Then they see "Link expired, request a new one"

Given a user enters a weak password (e.g., "pass")
When they click "Update Password"
Then validation error appears: "Password must be 8+ chars with uppercase and number"

Read the full file on GitHub · 163 lines

Changes

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.

  1. 7d ago First seen · 163 lines · 49 tokens per session scan A 9b00c99883e4

Subscribe to this mod's changes

acceptance-criteria is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 1,194 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-09-03.

Related

Other skills, from other repositories

aw

Ships autonomous, end-to-end coding work — implement a feature or fix, all the way to a tested draft PR — from a single opt-in entry point. Detects the task tier (Micro / Lite / Full) and routes: Micro/Lite run single-pass in this context; Full hands off to the aw-planner → aw-executor agents. Use when the user asks…

mthines/agent-skills · 193 tokens

contract-testing-flywheel

Generate a structured onboarding backlog — in Jira, GitHub Issues/Projects, Azure DevOps, or as a manual markdown export — that drives a development team from zero to publishing both consumer and provider contract tests. Use when the user invokes /contract-testing-flywheel or asks to "kick off contract testing for a…

pactflow/pactflow-agent-skills · 144 tokens

ai-team-orchestration

Bootstrap and run a multi-agent AI development team. Use when: starting a new software project with AI agents, setting up parallel dev/QA teams, creating sprint plans, writing brainstorm prompts with distinct agent voices, recovering a project workflow, or planning sprints.

boshi-xixixi/TraeSkill · 58 tokens

openspec-implementation

A workflow for implementing an approved technical specification one task at a time. It reads the proposal, makes the changes, runs tests, and validates the result.

sutchan/Agent-Skills-Hub · 86 tokens

multi-role-quality-synthesis

Use this skill when multiple role reports for one quality stage must be combined into a traceable synthesis; triggers include multi-role quality synthesis, role report consolidation, disagreement summary..

naodeng/awesome-qa-skills · 40 tokens

project-delivery-perspective

Use this skill when project delivery constraints or action tracking are needed for test strategy, test strategy review, or test report review; triggers include project delivery perspective, delivery planning, schedule and capacity..

naodeng/awesome-qa-skills · 44 tokens