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 ALTEN-group/coding-pal --skill criteria-verifygit clone --depth 1 https://github.com/ALTEN-group/coding-palWrote 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/alten-group/coding-pal/criteria-verify)<a href="https://agentmods.dev/skills/alten-group/coding-pal/criteria-verify"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/criteria-verify/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/alten-group/coding-pal/criteria-verify"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/criteria-verify.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.00078 | $0.00603 |
| Opus 5.5 | $0.00031 | $0.00241 |
| Sonnet 5.5 | $0.00016 | $0.00121 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
criteria-verify 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 3d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Criteria Verify
Deterministic Criteria Test Verification gate. The Plan record lists acceptance criteria; this skill proves from the test reports that each one has a passing test. It runs no tests itself.
When to Use This Skill
- Code has finished a step or the whole plan, and the agent must know which acceptance criteria still lack a passing test.
- CI (Prove) must block a pull request when a criterion has no passing test, a mapped test failed, or the Test Plan's test file was not run.
- Tests must be named after the criteria they verify (
AC-<n>in the test name).
Path resolution
Resolve references/ and scripts/ relative to this skill's install directory (the folder that contains this SKILL.md), not the consumer repository root or the current shell cwd. If the skill was installed under .agents/skills/criteria-verify/ or .claude/skills/criteria-verify/, use that base path. Run the scripts from the repository root (so specs/ and reports/ paths resolve) and write <skill-dir> as that install path.
Workflow
- Read
references/criteria-verify-contract.mdnow. It is the authoritative source for the mapping rule, report formats, verdicts, and exit codes. - Name each test with the criterion it verifies, for example
it("AC-2 rejects viewers", ...), and make the test runner write a report (JUnit XML or Jest/Vitest JSON). - Run the gate from the repository root:
node <skill-dir>/scripts/verify-criteria.mjs --plan specs/issue-42/plan.md \
--report reports/jest.json --report reports/api-junit.xml --require-test-files
- Treat a nonzero exit as a failed gate. Read the
Unverified criterialist, then fix the code or the missing test. Never skip a test, edit the Test Plan, or change the script to obtain a pass. - In CI, run the same command against the clean-environment reports and let a failure trigger auto-remediation.
Done When
- The script exits 0: every
AC-<n>has at least one passing mapped test and no mapped test failed. - With
--require-test-files, every Test Plan test file appears in a report. - No test was skipped, removed, or renamed to hide a criterion.
What ships with it
4 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.
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.
- 3d ago First seen · 40 lines · 78 tokens per session scan A de27992d0f4a
criteria-verify is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 78 tokens to every session and 603 once invoked, about $0.0003 per session on Opus 5.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-10-14.
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.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
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".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
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.