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 majiayu000/claude-skill-registry --skill ac-criteria-validatorgit clone --depth 1 https://github.com/majiayu000/claude-skill-registryWrote 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/majiayu000/claude-skill-registry/ac-criteria-validator)<a href="https://agentmods.dev/skills/majiayu000/claude-skill-registry/ac-criteria-validator"><img src="https://agentmods.dev/badge/skills/majiayu000/claude-skill-registry/ac-criteria-validator/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/majiayu000/claude-skill-registry/ac-criteria-validator"><img src="https://agentmods.dev/badge/skills/majiayu000/claude-skill-registry/ac-criteria-validator.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.00033 | $0.00616 |
| Opus 5 | $0.00016 | $0.00308 |
| Sonnet 5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
ac-criteria-validator 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 13d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AC Criteria Validator
Validate acceptance criteria and determine feature completion.
Purpose
Validates that implemented features meet their acceptance criteria, determining when passes can transition from false to true.
Quick Start
from scripts.criteria_validator import CriteriaValidator
validator = CriteriaValidator(project_dir)
result = await validator.validate_feature("auth-001")
print(result.passes) # True/False
print(result.criteria_results)
Validation Result
{
"feature_id": "auth-001",
"passes": true,
"criteria_results": [
{
"criterion": "Valid registration creates user",
"passed": true,
"evidence": "test_valid_registration passed",
"method": "test_execution"
},
{
"criterion": "Invalid email shows error",
"passed": true,
"evidence": "test_invalid_email passed",
"method": "test_execution"
}
],
"test_summary": {
"total": 5,
"passed": 5,
"failed": 0,
"coverage": 87.5
},
"validated_at": "2024-01-15T10:30:00Z"
}
Validation Methods
Test Execution
- Run associated test files
- Check all tests pass
- Verify coverage threshold
- Capture test output
Code Analysis
- Check implementation exists
- Verify function signatures
- Validate error handling
- Check documentation
Manual Criteria
- UI/UX requirements
- Performance benchmarks
- Security requirements
- Accessibility standards
Validation Rules
validation:
require_all_tests_pass: true
minimum_coverage: 80
require_no_lint_errors: true
require_type_checks: true
custom_rules:
- name: "no_console_logs"
pattern: "console\\.log"
severity: "warning"
Workflow
- Load: Get feature and criteria
- Discover: Find related tests
- Execute: Run test suite
- Analyze: Check each criterion
- Report: Return validation result
State Transition
CRITICAL: passes can ONLY transition false → true
Before validation:
{"passes": false, "status": "in_progress"}
After successful validation:
{"passes": true, "status": "completed"}
NEVER:
{"passes": true} → {"passes": false}
What ships with it
1 file 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.
- 13d ago First seen · 122 lines · 33 tokens per session scan A 43e92f491d56
ac-criteria-validator is a skill published in the GitHub repository majiayu000/claude-skill-registry (604 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 616 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-30.
Other skills, from other repositories
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
iso-write
Implement a written plan using TDD, without committing. Use when invoked as /iso-write [--no-branch | --branch= | --worktree] or handed an implementation plan to build. By default it resumes or cuts a branch derived from the plan filename only when the current branch is a base branch (dev, develop, test, prod, main…
test-report-review
Use this skill when a test report needs an evidence-consistency review before Human approval; triggers include test report review, quality report audit, test evidence review..
ux-quality-perspective
Use this skill when a quality stage needs a UX perspective on information architecture, interaction states, consistency, responsive behavior, or accessibility; triggers include UX quality perspective, UX review..
agent-tool-testing
Use this skill when you need to test AI agent tool-call contracts, authorization, failures, and side-effect boundaries; triggers include agent tool testing.
test-case-writing
Use this skill when you need to create high-quality test cases with normal, exception, and boundary scenarios; triggers include test case writing and test design.