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 aigentive/RalphX --skill acceptance-criteria-writinggit clone --depth 1 https://github.com/aigentive/RalphXWrote 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/aigentive/ralphx/acceptance-criteria-writing)<a href="https://agentmods.dev/skills/aigentive/ralphx/acceptance-criteria-writing"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/acceptance-criteria-writing/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/aigentive/ralphx/acceptance-criteria-writing"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/acceptance-criteria-writing.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.00015 | $0.00648 |
| Opus 5 | $0.00008 | $0.00324 |
| Sonnet 5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
acceptance-criteria-writing 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 9d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acceptance Criteria Writing
Guidelines for generating clear, testable acceptance criteria from task specifications.
What Makes Good Acceptance Criteria
SMART Criteria
- Specific: Describes exactly what should happen
- Measurable: Has a clear pass/fail condition
- Achievable: Can be implemented as specified
- Relevant: Directly relates to the task
- Testable: Can be verified with agent-browser
Bad vs Good Examples
Bad: "The UI looks nice" Good: "The task card displays title, status badge, and priority indicator"
Bad: "Performance is acceptable" Good: "Task list loads within 2 seconds for 100 tasks"
Bad: "Drag and drop works" Good: "Dragging a task to the Planned column triggers the planned animation"
Criteria Types
Visual (type: "visual")
UI appearance and layout requirements.
- Element visibility
- Layout structure
- Color/styling (when specified)
- Responsive behavior
Examples:
- "Task board displays 7 columns"
- "Each column has a header with task count"
- "Task cards show status icon"
Behavior (type: "behavior")
User interaction outcomes.
- Click actions
- Form submissions
- Drag-drop operations
- Keyboard navigation
Examples:
- "Clicking a task opens the detail panel"
- "Submitting form creates new task"
- "Pressing Escape closes modal"
Data (type: "data")
Data display and accuracy.
- Correct values displayed
- Data persistence
- State synchronization
Examples:
- "Task title matches input value"
- "Task count updates after creation"
- "Status reflects backend state"
Accessibility (type: "accessibility")
A11y requirements.
- ARIA labels
- Focus management
- Screen reader support
Examples:
- "All interactive elements have aria-labels"
- "Focus moves to modal when opened"
- "Tab order follows visual layout"
Output Format
{
"acceptance_criteria": [
{
"id": "AC1",
"description": "Specific testable statement",
"testable": true,
"type": "visual"
}
]
}
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.
- 9d ago First seen · 120 lines · 15 tokens per session scan A 1f6893f338d4
acceptance-criteria-writing is a skill published in the GitHub repository aigentive/RalphX (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 15 tokens to every session and 648 once invoked, about $0.0001 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.