Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/aget-framework/template-advisor-agetnpx agentmods add skills/aget-framework/template-advisor-aget/aget-release-audit-specsWrote 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/template-advisor-aget/aget-release-audit-specs)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-release-audit-specs"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-release-audit-specs/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/template-advisor-aget/aget-release-audit-specs"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-release-audit-specs.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.00000 | $0.01394 |
| Opus 5 | $0.00000 | $0.00697 |
| Sonnet 5 | $0.00000 | $0.00279 |
| Haiku 4.5 | $0.00000 | $0.00139 |
Grade A, and why
aget-release-audit-specs 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 10d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818). Coverage and consistency mode.
Purpose
The Spec Auditor asks: "Does this spec cover all behaviors? Are there gaps or contradictions?"
This skill shifts your cognitive posture to prioritize specification quality — finding gaps, inconsistencies, and missing coverage. You are the Spec Auditor — read every requirement, verify every cross-reference, surface every sleeping requirement.
You do NOT execute deliverables (that is /aget-release-build). You do NOT adversarially test assumptions (that is /aget-release-critique). You audit specifications.
Triggers
- "audit specs", "audit specifications"
- "spec coverage check"
/aget-release-audit-specs
Input
Optional: gate number, specific spec paths, or PROJECT_PLAN path. If omitted, audit all specs touched in the current gate.
Execution
Step 1: Identify Specs in Scope
From the Builder's report (if available) or the PROJECT_PLAN, identify:
- Specs created in this gate
- Specs modified in this gate
- Specs referenced by deliverables but not modified
Step 2: Coverage Audit
For each spec in scope, check:
Completeness:
- All requirements use EARS patterns (SHALL/WHEN/WHERE) or equivalent
- V-test IDs assigned to testable requirements
- No orphan requirements (referenced but undefined)
- No duplicate requirement IDs
Consistency:
- Cross-references between specs are bidirectional and valid
- Terminology is consistent (check against GOVERNED_TERM_MAPPING.yaml)
- Version numbers in references match actual file versions
- No contradictions between requirements in different specs
Coverage:
- All behaviors described in prose have corresponding formal requirements
- Sleeping requirements detected (requirement exists but no enforcement — L671/CAP-VOC-002-01)
- Gap between spec claims and SOP/ADR governance alignment
Step 3: Spec Audit Report
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.
- 10d ago First seen · 154 lines · 0 tokens per session scan A daa66f4720fe
aget-release-audit-specs is a skill published in the GitHub repository aget-framework/template-advisor-aget (2 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,394 tokens. 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
tt-sidebar
Open a live Token Tracker sidebar for only the current Codex session in a right-side terminal split at one-third width. Use when the user explicitly invokes $tt-sidebar or asks to monitor the current Codex session beside its terminal pane.
modern-python-toolchain
Modern Python project setup with uv, ruff, and pyright. Use when initializing a new Python project, configuring the Python environment, setting up linting/formatting, or when a project needs uv (the fast Python package manager). Trigger on: 'set up Python', 'new Python project', 'configure uv', 'install uv', 'ruff'…
gap-analyzer
Compares a CLI's implemented commands against its APP.md API map and traffic-analysis.json to find missing endpoints, incomplete CRUD, dead client methods, and priority gaps. Runs as the mandatory first step of /cli-anything-web:refine and as an optional pre-review scan in standards.
airbnb-cli
Use cli-web-airbnb to search Airbnb stays, get listing details, check availability calendars, read guest reviews, and look up location suggestions. Invoke this skill whenever the user asks about Airbnb accommodations, vacation rentals, listing prices, availability, guest reviews, or wants to search for places to stay.…
linkedin-cli
Interacts with LinkedIn via the cli-web-linkedin command-line tool — search people/jobs/companies, view profiles and feed, create/edit/delete posts, react and comment, manage connections and invitations, read and send messages, view notifications, follow companies. Use when the user asks about LinkedIn or wants to…
notebooklm-cli
Drives Google NotebookLM via the cli-web-notebooklm command-line tool — create and manage notebooks, add URL/text sources, ask questions grounded in the sources, and generate/download artifacts (audio overview, video, slide deck, mindmap, study guide, quiz, FAQ, briefing, infographic, data table). Use when the user…