Borrowing it
Nothing to install: this file belongs to aget-framework/aget. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aget-framework/aget/main/.claude/skills/aget-validate-spec/SKILL.mdgit clone --depth 1 https://github.com/aget-framework/agetWrote 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/aget-framework/aget/aget-validate-spec)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-validate-spec"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-validate-spec/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/aget-framework/aget/aget-validate-spec"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-validate-spec.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.00011 | $0.00732 |
| Opus 5.5 | $0.00004 | $0.00293 |
| Sonnet 5.5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
aget-validate-spec 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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aget-validate-spec
Validate specifications for completeness, consistency, and testability. Ensures EARS format compliance.
Instructions
When this skill is invoked:
-
Check Completeness
- Required sections present
- All requirements have IDs
- Traceability links exist
-
Check Consistency
- No contradictions
- Terminology consistent
- IDs unique
-
Check Testability
- Requirements are verifiable
- Acceptance criteria clear
- No vague language
-
Check Format
- EARS templates applied
- Correct SHALL/SHOULD usage
- Proper structure
Required Sections
- Scope
- Requirements (functional)
- Constraints (non-functional)
- Traceability
- Test cases or V-tests
EARS Patterns
| Pattern | Template |
|---|---|
| Ubiquitous | The [system] SHALL [action] |
| Event-Driven | WHEN [event], the [system] SHALL [action] |
| State-Driven | WHILE [state], the [system] SHALL [action] |
| Conditional | IF [condition], the [system] SHALL [action] |
Output Format
## Specification Validation: [Spec Name]
### Overview
| Attribute | Value |
|-----------|-------|
| Spec | [Name] |
| Version | [X.Y.Z] |
| Validator | [Agent] |
| Date | [YYYY-MM-DD] |
---
### Completeness Check
| Section | Status | Notes |
|---------|--------|-------|
| Scope | [Present/Missing] | |
| Requirements | [Present/Missing] | [N] requirements |
| Constraints | [Present/Missing] | [N] constraints |
| Traceability | [Present/Missing] | |
| Tests | [Present/Missing] | [N] tests |
---
### Consistency Check
| Check | Status | Issues |
|-------|--------|--------|
| No contradictions | [Pass/Fail] | [Details] |
| Terminology | [Pass/Fail] | [Details] |
| Unique IDs | [Pass/Fail] | [Details] |
---
### Testability Check
| Requirement | Testable | Issue |
|-------------|----------|-------|
| R-XXX-001 | [Yes/No] | [Why not testable] |
---
### EARS Format Check
| Requirement | Pattern | Compliant | Issue |
|-------------|---------|-----------|-------|
| R-XXX-001 | [Pattern] | [Yes/No] | [Issue] |
---
### Summary
**Status**: [Valid / Issues Found]
**Blocking Issues**: [N]
**Warnings**: [N]
**Required Actions**:
1. [Action 1]
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.
- 1mo ago First seen · 132 lines · 11 tokens per session scan A 9ef33346d51b
aget-validate-spec is a skill published in the GitHub repository aget-framework/aget (12 stars, last pushed 7d ago), licensed Apache-2.0. It adds 11 tokens to every session and 732 once invoked, about $0.0000 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-09-03.
Other skills, from other repositories
tdd
Drive a red → green → refactor cycle for the active task.
aget-close-project
Close a PROJECTPLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECTPLAN…
aget-release-critique
Adversarial review with the Critic perspective of the Release Delivery Triad (L818). Dual mandate — spec coverage audit plus deep bug finding, asking what breaks in the field and which assumptions are wrong. Superseded by /aget-check-release.
aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818) — coverage and consistency mode, asking whether a spec covers all behaviors and where gaps or contradictions remain. Superseded by /aget-check-release.
aget-release-build
Execute release gate deliverables with the Builder perspective of the Release Delivery Triad (L818) — speed-optimized execution asking whether the work is done, fast, and functional. Superseded by /aget-create-release.
aget-file-issue
File issues with L520 governance compliance.