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-enhance-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-enhance-spec)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-enhance-spec"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-enhance-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-enhance-spec"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-enhance-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.00039 | $0.04133 |
| Opus 5 | $0.00019 | $0.02067 |
| Sonnet 5 | $0.00008 | $0.00827 |
| Haiku 4.5 | $0.00004 | $0.00413 |
Grade A, and why
aget-enhance-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- aget-enhance-spec — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-enhance-spec
Guide agents through the core specification enhancement lifecycle. Provides governed workflow for spec creation, updates, cross-reference wiring, and validation.
Purpose
Replace ad-hoc specification enhancement with a repeatable, governed 7-phase process derived from 5 independent plans across 3 agents (L622). This is the Generator layer (ADR-008 step 3), built on SOP_specification_enhancement.md (Advisory) and SKILL-041 spec (Strict).
Input
$ARGUMENTS - Enhancement category and optional spec path.
Format: <CATEGORY> [spec-path] [--version <target-version>]
Categories: NEW, UPDATE, ADD-REQ, WIRE, CONSOLIDATE, DEPRECATE
Examples:
/aget-enhance-spec NEW specs/AGET_FOO_SPEC.md/aget-enhance-spec UPDATE aget/specs/AGET_SOP_SPEC.md --version 1.2.0/aget-enhance-spec WIRE aget/specs/SKILL_NAMING_CONVENTION_SPEC.md/aget-enhance-spec ADD-REQ aget/specs/AGET_SOP_SPEC.md
Phase Selection
Not all categories require all phases. Use this table to determine which phases to execute:
| Category | Required Phases |
|---|---|
| NEW | 0, 1, 2, 3, 4, 5, 6 (all) |
| UPDATE | 0, 1, 2, 3, 4, 5, 6 (all) |
| ADD-REQ | 0, 1, 2, 3, 4, 5, 6 |
| WIRE | 0, 1, 5, 6 |
| CONSOLIDATE | 0, 1, 2, 3, 4, 5, 6 + reference SOP_specification_consolidation.md |
| DEPRECATE | 0, 1, 3, 6 |
Execution
Step 1: Parse Input
IF no arguments provided:
Prompt: "What type of enhancement? (NEW, UPDATE, ADD-REQ, WIRE, CONSOLIDATE, DEPRECATE)"
Prompt: "Path to spec? (leave blank for NEW)"
IF category not in valid list:
Error: "Invalid category. Valid: NEW, UPDATE, ADD-REQ, WIRE, CONSOLIDATE, DEPRECATE"
IF category in (UPDATE, ADD-REQ, WIRE) AND no spec path:
Error: "Spec path required for {category} enhancements"
Determine phase list from Phase Selection table above.
Step 2: Phase 0 — Trigger & Diagnosis
Objective: Identify the specification gap and gather evidence.
Execute:
- If spec path provided, read the spec file and extract current version, status, requirement count
- Search for related L-docs:
grep -l "<topic_keywords>" .aget/evolution/L*.md - Search for related specs:
ls specs/ aget/specs/ 2>/dev/null | grep -i "<topic>" - Document findings as evidence table:
| Evidence | Source | Impact | |----------|--------|--------| | <finding> | <L-doc or spec> | <why this matters> |
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 · 434 lines · 39 tokens per session scan A ba90b6098169
aget-enhance-spec is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 4,133 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
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 + deep bug finding.
aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818). Coverage and consistency mode.
aget-file-issue
File issues with L520 governance compliance.
aget-release-build
Execute gate deliverables with the Builder perspective of the Release Delivery Triad (L818). Speed-optimized execution mode.
aget-propose-actions
Propose ranked next-best actions with evidence grounding, time budgets, and execute-all default. Formalizes the fleet's highest-frequency interaction pattern.