What is spec-quality?

A quality checklist for scenario-based software specifications. It checks that a specification describes observable behavior and reasons clearly without turning into an implementation plan or test file.

Drafting or reviewing product and implementation specifications, Given/When/Then scenarios, Proposed Surface sections, open questions, and spec-quality checklists.

It helps teams detect vague, duplicated, overly technical, or untestable requirements before implementation begins.

spec-quality — Skill for Claude Code and Codex by hams-ollo

Install

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.

Any agent

npx skills add hams-ollo/zen-agent-skills --skill spec-quality

Clone the repo

git clone --depth 1 https://github.com/hams-ollo/zen-agent-skills

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/spec-quality/github.svg)](https://agentmods.dev/skills/hams-ollo/zen-agent-skills/spec-quality)

Your own site

<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/spec-quality"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/spec-quality/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/spec-quality"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/spec-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,236 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00077	$0.02236
Opus 5	$0.00039	$0.01118
Sonnet 5	$0.00015	$0.00447
Haiku 4.5	$0.00008	$0.00224

Measured 5d ago against content hash ab370e01c2e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

spec-quality 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 5d 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.

.agents/skills/spec-quality/SKILL.md · 226 lines

How it starts

The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spec quality

Adapted from repoprompt-workflows (Balarama Bosch), MIT.

Intent

Help agents draft and review specs that are contract-level, scenario-driven, testable, non-redundant, and grounded in existing repository context.

A good spec says what behavior should exist and why it matters. It does not become the implementation plan, architecture brief, task list, or test file design.

This skill is a lens, not a drafting workflow: it is meant to be composed into one. spec-author drafts specs and calls this lens to check its own output before returning it.

When to use

Use this skill when working on any scenario-based spec or spec-like draft, including:

product or implementation specs;
Problem, Goals, Non-Goals, Constraints, Scenarios, Proposed Surface, or Open Questions sections;
Given/When/Then scenarios;
spec review, repair, validation, or quality checklists.

This skill can guide drafting or return a quality report. It does not replace a repo's explicit Spec workflow when that workflow is responsible for writing files, naming specs, or updating spec indexes.

Inputs

Required:

Spec draft or source request: readable spec content, proposed spec sections, scenarios, or a user request for a future spec.

Optional:

Repository context: existing names, tools, commands, APIs, docs, schemas, or conventions that should ground the spec wording.

If no spec draft or source request is supplied, or the supplied input cannot be interpreted as spec-related content, report input_error and do not return ready.

Non-goals

Do not use this skill to:

replace an explicit Spec workflow that writes spec files (for example under a repo's docs/spec/ convention) or updates spec indexes;
write spec files (e.g. under docs/spec/) unless the user explicitly asks for file edits;
update a spec index such as docs/spec/README.md;
create implementation plans, architecture documents, code, or tests;
decide feature implementation details that belong to planning or design;
judge readiness of a Spec plus Deep Plan pair; use a dedicated spec-plan-readiness process for that.
judge whether an implementation conforms to a spec (spec-vs-implementation); use spec-conformance for that, or doc-sync for doc-vs-code drift.

Read the full file on GitHub · 226 lines

Changes

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.

5d ago Changed · +7 lines ab370e01c2e8
9d ago First seen · 219 lines · 77 tokens per session scan A 9cd3fec4c836

Subscribe to this mod's changes

spec-quality is a skill published in the GitHub repository hams-ollo/zen-agent-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 77 tokens to every session and 2,236 once invoked, about $0.0004 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.

Claude Code Planning Writing and docs agent-skills agents-md ai-agents developer-tools spec-driven-development

implementation-standards

Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.

attilaszasz/sdd-pilot · 44 tokens

quality-assurance

Reference material with consistency-analysis heuristics and checklist-management rules. Loaded on demand by analyze-compliance and quality-control; not directly invokable.

attilaszasz/sdd-pilot · 36 tokens

instructions-management

Manages the project instructions — a document of non-negotiable project principles and governance rules. Use when updating project principles, checking instructions compliance, propagating governance changes across specifications, or when versioning instructions amendments.

attilaszasz/sdd-pilot · 46 tokens

spec-quality