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 pantheon-org/tekhne --skill acceptance-criteriagit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/acceptance-criteria)<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.
<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>- NVIDIA SkillSpector pass
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.00049 | $0.01194 |
| Opus 5 | $0.00024 | $0.00597 |
| Sonnet 5 | $0.00010 | $0.00239 |
| Haiku 4.5 | $0.00005 | $0.00119 |
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.
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
- Capture user outcome and business intent.
- Select criteria format (Given/When/Then or rule-oriented).
- Draft must-pass criteria with measurable outcomes.
- Add negative and boundary scenarios.
- 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"
What ships with it
34 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.
- .audits/2026-02-21/analysis.md 8.1 KB
- .audits/2026-02-21/audit.json 145 B
- .audits/2026-02-21/remediation-plan.md 234 B
- .audits/2026-02-22/analysis.md 8.1 KB
- .audits/2026-02-22/audit.json 145 B
- .audits/2026-02-22/remediation-plan.md 234 B
- .audits/2026-02-23/analysis.md 8.1 KB
- .audits/2026-02-23/audit.json 146 B
- .audits/2026-02-23/remediation-plan.md 230 B
- .audits/2026-03-02/analysis.md 1.0 KB
- .audits/2026-03-02/audit.json 418 B
- .audits/2026-03-02/remediation-plan.md 2.1 KB
- .audits/latest 10 B
- evals/instructions.json 4.3 KB
- evals/scenario-01.md 4.3 KB
- evals/scenario-01/capability.txt 144 B
- evals/scenario-01/criteria.json 1.4 KB
- evals/scenario-01/task.md 241 B
- evals/scenario-02.md 4.7 KB
- evals/scenario-02/capability.txt 175 B
- evals/scenario-02/criteria.json 1.4 KB
- evals/scenario-02/task.md 272 B
- evals/scenario-03.md 5.1 KB
- evals/scenario-03/capability.txt 164 B
- evals/scenario-03/criteria.json 1.7 KB
- evals/scenario-03/task.md 323 B
- evals/scenario-04.md 5.3 KB
- evals/scenario-05.md 5.3 KB
- evals/summary.json 860 B
- references/examples.md 510 B
- references/gherkin-examples.md 1.8 KB
- references/invest-criteria.md 503 B
- references/patterns-by-type.md 1.9 KB
- references/templates.md 400 B
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.
- 7d ago First seen · 163 lines · 49 tokens per session scan A 9b00c99883e4
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.
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…
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…
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.
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.
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..
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..