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 Eliyce/paqad-ai --skill spec-quality-reviewgit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/spec-quality-review)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/spec-quality-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/spec-quality-review/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/eliyce/paqad-ai/spec-quality-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/spec-quality-review.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.00017 | $0.00641 |
| Opus 5 | $0.00009 | $0.00320 |
| Sonnet 5 | $0.00003 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
spec-quality-review 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 7d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Surfaces likely spec defects — contradictions, formula inconsistencies, boundary gaps, goal conflicts, dangling references, and missing negative cases — as a human-readable list, so an author can fix them before freezing. It is an optional pre-pass, not the gate: paqad-ai spec freeze runs the authoritative, deterministic spec-quality review itself and blocks on a critical defect (issue #401). This skill neither persists a report nor hands anything authoritative downstream.
Use This When
Use this after a spec edit and before you run paqad-ai spec freeze, or when an implementation bug suggests the spec may be internally inconsistent, to catch defects early rather than at freeze time. Skipping it changes nothing about the freeze — the freeze runs its own review regardless.
Inputs
- Read the target spec markdown file in full.
- Read
references/spec-defect-checklist.mdbefore issuing findings. - Use
agents/openai.yamlfor the reasoning contract when the workflow executes through agent infrastructure.
Procedure
- Run
scripts/scan-defects.sh <spec.md>— it skips Open Questions and TBD lines and emits candidate hits across the categories inassets/categories.txt(vague-quantifier, missing-actor, unbounded-modal, tbd-leak, dangling-ref, goal-collision, no-negative). - Confirm each hit (or dismiss with a reason) — the script flags candidates, you judge severity.
- Format a markdown summary per
assets/output.template.md; validate it withscripts/lint-output.sh. - Order findings by severity, then by source line.
Output Contract
- Return a
## Findingssection listing active defects with severity, category, location, and the specific clarification or rewrite needed. - Return a
## Resolvedsection only when a prior finding is now absent; omit it otherwise. - Persist nothing. This pre-pass writes no
spec-review.jsonand no.paqad/compliance/**file — the freeze owns the authoritative record (its defect summary is folded into the bundle'sspecification.json).
What ships with it
6 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.
- 7d ago Changed · -2 lines · +4 tokens per session 8622e6838fc3
- 12d ago First seen · 61 lines · 13 tokens per session scan A 0ac3530a1acc
spec-quality-review is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 641 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
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-go
A command that implements code from a SPEC, a document describing the required behavior and work.
auto-plan
A code-planning skill that examines a codebase and creates a detailed specification, implementation plan, and acceptance criteria. It can organize requirements using EARS, a structured way to describe how software should behave in different situations.
agent-pipeline
Multi-agent pipeline orchestration skill.
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.